What JavaScript framework should I use?

Source: tildes.net
12 points by delphi 16 days ago on tildes | 29 comments

Little backstory. I'm the sole developer of delphitools, a collection of free and open source tools for artists, developers and just computer touchers in general. I'm using Next.JS and as such, React, but I don't think I like it anymore. DT is a completely offline exported application, and Next is meant for middleware-heavy apps with server layers, which I just don't have. I also just don't get on with React's endless use effect garbage and have little love for TypeScript, and if I'm honest, DT happens to be made like that because I wanted to try the shiny new thing. Now that I have around 60-ish individual micro-apps contained within, I think it's time for a rewrite.

I'm therefore looking for discussion and insights on what tooling is best for me, on the following grounds:

  1. delphitools is export only. There's no server component and it runs completely in the browser. Server capabilities or middleware are not a concern.
  2. I'm not married to JavaScript as the runtime. It's just what I know best, I've been in the industry for a long time, although I'm more familiar with classic JS, not necessarily the JSX react syntax. I'm confident I could learn something new though.
  3. I'm looking for fast build times, a smart-ish compiler that can ideally hot reload and give me insights into bad practices (Next.JS does this quite well)
  4. As close to bare metal as possible, I can't begin to enumerate the amount of times the NextJS Turbopack auto-caching thing has caused me significant headaches.

I'm a designer, not a developer, but I can manage my way around. I'm also not opposed to using Agents, but I would like to - if for my own sake more than anything - be able to work without them if need be. Suggesting Ruby that compiles to HTML or some other crazy new pipeline probably won't work.

Curious to hear your experiences and recommendations. Thanks!