My nation-wide C# Silverlight app lasted almost 12 years. And it had grid, animations, what have you in 2010 better than most html5 in 2018. Not to mention tooling.

And you know what? No matter the browser, no matter the OS it all worked and rendered the same.

Probably Adobe Flash was like that also.

First app we rewrote to AngularJS. You know what happened to it. So then we rewrote it to Vue.

The same effing app just to keep the stack “modern”.

I don’t know what is wrong with all these people.

God I wish something like Silverlight returned in a way that is mobile battery friendly.

I picked React over Angular in 2015 and havn’t looked back. I’ve never done, nor been asked to do a rewrite. I once interviewed for a role that would have involved a rewrite from Angular to React. My current employer has a design system and UI library to implemenet it. Some time before I joined, they decided to move from Stencil-driven support for React, Angular and one other framework, to pure React support. From 50-60 applications I made late 2024-2025 one used Lit one Svelt, maybe 10-15 Angular and the rest React. In previous rounds of job or contract hunting, I don’t recall seeing demand for anything other than the big two.

I live and work in London. I’ve basically not seen this culture of constant churn and rewrites that people on HN bemoan since about 2018.

I think Vue.js has done a great job of avoiding a lot of the churn while staying competitive with other projects in terms of features and performance.

The core library of React seems well managed, but the accompanying ecosystem of 3rd-party tools for styling, routing, state management, etc seem to be constantly changing.

Meanwhile in Vue land, the critical packages have remained fairly stable and are all maintained by the core team. You get support for styling and transitions out of the box; for most other things (routing, state management, etc) there is one well-maintained library (as opposed to a bunch of options of varying quality that you need to sift through).

I've been using Vue.js for 10 years at this point, and have been using the composition API for the last 5. The older options API is still viable as well.

Javascript is not a language that is good for making basic comprehensive abstractions in.

Typescript is not a language that is good for making basic comprehensive abstractions in.

JSX is not a language that is good for making basic comprehensive abstractions in.

To be really honest. AI / LLM's can write svelte 5 runes code but Its a really really mixed bag and most of them probably write svelte 4 code

Like, here's the thing, sure it can create the code but LLM's stop so early in things like svelte atleast that's my opinion. I never really learnt react and didn't ever use react with any LLM

fun fact: Chatgpt 3 could write perfectly well sveltekit, that's how I "vibecoded" in the start

Like, sure I would copy paste but deep down I just felt like most of this is just plain html css js and nothing too much to worry about and that soothed me that sure this may be vibe coded but I was a real noob of svelte but the vibe coding was a bit of a successful :p

I have stopped it / atleast reminded myself 100 times to stop it because I want to feel even more confident with svelte and really learn it even more to the point that I can be 100% confident to write complex software in svelte myself and well only using AI for the boilerplate part or the tedious parts I am not sure, there is a lure to ask LLM's more and more and to depend on them more or maybe its just me I am not sure.

React has been pretty stable for many years now and is almost ubiquitous.

Also, I'm not a huge fan of synthetic benchmarks like in the article such as "render a static list of 25000 elements". This never happens in the real world, you would use some implementation of a virtual list instead.

Yes, don’t tell me this. I have to rewrite PHP based website because a framework doesn’t work with new PHP anymore. Back compatibility sucks in many software.