quickjs VS daisyui

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.)

If you're using a component library like daisyUI, you can map styling options directly to its semantic classes btn-primary, bg-base-200). This gives you theme switching for free — every block re-skins automatically when the theme changes.

DaisyUI[0] is the Bootstrap on Tailwind.

Bootstrap makes everything looks the same. With Tailwind, most of the times and besides the colors, you have to look in the code to know it's Tailwind.

[0]https://daisyui.com/

Instead, I'm going with DaisyUI. It is a nice UI library with ready-to-use components and utilities. The best part? You can just include it via CDN—no setup needed.

Complete UI refresh, using DaisyUI

I later discovered DaisyUI, which provides a theme system on top of Tailwind. Instead of using color names like bg-blue-500, you can use semantic names like bg-primary and then define what primary means in your theme.

In addition to that, there have been various other derivative UI kits such as Daisy UI, Flowbite, Aceternity UI, and Retro UI. These have led to so many profitable businesses and made Tailwind CSS hugely popular among new developers.

DaisyUI

check out daisy-ui (https://daisyui.com) if must use TailWind.