quickjs VS Django

You don't need V8 for running JS for scripting, you have quickjs[1] or mquickjs[2] for example. You might have problems importing npm packages, but as we can see from lua plugins you don't even need support for package managers. Performance is not as good as luajit, but it is good enough

[1]: https://bellard.org/quickjs/

[2]: https://github.com/bellard/mquickjs

It wasn't a QuickJS developer but developer from a fork: https://github.com/bellard/quickjs/issues/445

I see a few mentions of QuickJS, but they all refer to the fork of Bellard's QuickJS https://bellard.org/quickjs/, which I think deserves a mention. It seems to be still active (last release 2025-04-26, GitHub mirror at https://github.com/bellard/quickjs shows some activity).

This is a fantastic approach.

BTW, it looks like the js engine is "QuickJS" [0]. (I'm not familiar with it myself.)

I like it because sqlite by itself lacks a host language. (e.g., Oracle's plsql, Postgreses pgplsql, Sqlserver's t-sql, etc). That is: code that runs on compute that is local to your storage.

That's a nice flexible design -- you can choose whatever language you want. But quite typically you have to bring one, and there are various complications to that.

It's quite powerful, BTW, to have the app-level code that acts on the app data live with the data. You can present cohesive app-level abstraction to the client (some examples people will hopefully recognize: applyResetCode(theCode) or authenticateSessionToken(), or whatever), which can be refined/changed without affecting clients. (Of course you still have to full power and flexibility of SQL and relational data for the parts of your app that need it.)

[0] https://bellard.org/quickjs/

Considering the extremes of prolific developers gives interesting contrast to dogmas such as "functions/files should never be above x lines", where `quickjs.c` is 50k lines and has functions that are hundreds of lines long:

https://github.com/bellard/quickjs/blob/master/quickjs.c

(Obviously different approaches suites different circumstances.)

PR: Link This is very interesting bug. You can perform coalesce to receive not-null first value from given columns fetching. However, column's type are vary. Let imagine you coalesce Column A (string), Column B (JSON).

For Django applications, this goes at the top of the settings module so it runs during framework initialization. If any variable is missing, the process exits before any application code loads. For Flask and FastAPI applications, the validation call belongs in the application factory before the app instance is created, so that any configuration-dependent setup fails with a clear message rather than a partially-initialized application.

This week's post is less technical, a reflection of the journey so far, while I celebrate my first PR merged and wait for two more to be reviewed.

One interesting thing about this ticket, is that there was in fact a PR created addressing it, 8 years ago! A few years later, it was closed due to inactivity.

I have built a library for the Django framework that simplifies the process of accepting crypto payments for your e-commerce (and other) applications.

The PR from the previous week is currently being reviewed, with some great suggestions from one of the Django fellows, Jacob Walls.

Anyway, to send code back to Django as future Pull Requests, first I need to create a "fork" of Django, which is a copy of its repository at https://github.com/django/django. To create the fork I just had to click on the "Fork" button

Laravel, Rails, and Django remain the most battle-tested full-stack frameworks in 2026.

Then came Python. And with that came Django, an opinionated framework. Really the opposite side of Zend Framework (which is just a grab-bag of tools with a consistent interface). And it was not just Django that has opinions, Python itself as well. A vision of the core values of the language: The Zen of Python.

Django (web framework with long-term stability): https://github.com/django/django