4 ms·
Yes it’s the echo chamber of the promotion funnels that makes it appear as if everyone were jumping ship every few days. In my bubble, Angular and React are th
by jmaker 3y ago
Yes it’s the echo chamber of the promotion funnels that makes it appear as if everyone were jumping ship every few days.
In my bubble, Angular and React are the primary frontend frameworks, with Vue sometimes being ahead and sometimes behind either. Virtually no one uses Svelte in my circles., but most folks have heard of it or have applied it in their side projects. HTMX is even more niche, still up for discovery for most folks, don’t know it well enough to comment. I prefer Vue and Angular DX but I favor React component libraries, it’s complicated. My absolute favorite is PureScript with React.
In most cases, backend is Spring on Java for well-defined or rather systematically approached applications, and Python or TypeScript for something that can run on AWS Lambdas and a junior dev might become responsible for. I think .NET is a no less decent choice for that matter. Go for rather small applications that need to touch on layers beneath the application layer, not the best choice to express complex business logic. I personally just pick the JVM stack with Kotlin and Spring, and deploy to AWS.
Rust is too unstable for long-term maintenance but deserves to be respected, I try to push Rust (though I’ve spent most of my time in C++) for smoother collaboration and simpler code review—there’s little I ever need to check after the Rust compiler—mostly the business logic and some axioms, in addition this raises the bar for quality contributions. Having to deal with low-key merges after the fact, sometimes even circumventing CI, is not pleasant at all.
Therefore, having the source of QA truth in the compiler is a boon to my productivity, hope it manages to obviate even more test suites, lifting more of the business logic into the type system, the way you can do it in Haskell or, even more powerful, Idris, but that’s a bit off-topic. Yet that’s what I choose if I need correctness.
- romanhn 3y agoGreat take. My project's tech stack is React on the frontend (without Next) and C# on the backend. For me this strikes the right balance of simplicity, performance, productivity and longevity.
- ralmidani 3y agoI doubt many advocates for htmx (or Hotwire) believe React is being abandoned right now. However, they do represent a serious challenge, because they’re not just marginally faster or more ergonomic like, say, Preact or Svelte - they represent a complete paradigm shift from how we’ve been building Web apps for the past ~decade. Being able to have over 80% of the interactivity you can get with React while expending perhaps 20% of the effort (no build step, no client-side data modeling and routing, no client-side state, easier for server-side oriented devs, use a language you’re already proficient in, reduced cognitive load, etc.) is huge. Many pioneering technologies are initially met with skepticism. A decade or so ago, jQuery was the clearly dominant client-side library. Very early adopters of React and its siblings were swimming against the tide, but eventually they made jQuery much less relevant. I’m not saying htmx will definitely become what React is today, but the belief that a dominant technology or paradigm is safe from disruption has been repeatedly proven wrong.