quickjs VS daisyui

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

And some lightweight alternatives like Bellard's QuickJS (https://bellard.org/quickjs/) in C and Kiesel (https://kiesel.dev/) in Zig.

Built on a highly optimized JavaScript runtime powered by QuickJS, Query offers fast startup times and efficient execution. Its built-in caching mechanism further enhances performance by storing function responses, reducing database load and latency. This focus on speed makes Query a standout choice for server-side rendering, especially in applications with many components.

Where the previous SDK was built on top of the QuickJS JavaScript engine and the Javy runtime, the new SDK is built on top of the Firefox browser’s SpiderMonkey engine, and the Bytecode Alliance’s StarlingMonkey runtime and ComponentizeJS WIT bindings generator.

I'm currently using Bellard's QuickJS engine on a new TypeScript project.

Then I learned Tauri and used my favourite frontend framework SolidJS with TailwindCSS and DaisyUI to build the UI with MotionOne to add animations and Tauri to build the desktop/web/android/ios app.

Other Tailwind Libraries: If the Shadcn approach isn't your jam, there are libraries like Flowbite or DaisyUI. They offer ready-made components styled with Tailwind, often installed as dependencies. Providing similar speed benefits for common patterns.

Explore DaisyUI

🔗 daisyUI Website

It’s difficult to go back to Material UI or Daisy UI in 2025 once you get into Shadcn. It became my go-to choice and potentially one of my primary reasons I’d opt for https://nextjs.org/ when I create a quick side-project or proof of concept.

However, using popular styling frameworks like TailwindCSS and DaisyUI inside the Shadow DOM isn’t straightforward. Since styles in the Shadow DOM don’t inherit from the global stylesheet, you need a strategy to ensure your component still benefits from Tailwind’s utility classes and DaisyUI’s prebuilt components.