[putnambr]

I've got a side project still on Svelte 3, I feel this. I got the implementation into a good state a few months ago and haven't needed to touch it, soon it will be two major versions behind. No regrets, no other framework was as easy to work with for a primarily SSR app.

I was feeling this with Quarkus too, but they finally set one of their recent versions as LTS. Setting an LTS and migration guides between LTSs is a practice I'd like to see more in front-end tech.

[khromov]

There's about a 99% chance you can update from Svelte 3 to 4 without any code changes. Some code changes are performed automatically by the migration script: https://svelte.dev/docs/v4-migration-guide

[azemetre]

Yeah I have a little personal Svelte app from the v3 days too, basically a simple form site that I use to choose boardgames during dinner parties.

It still works locally, been meaning to update it which I think will be painless as well because it's a dead simple site. No regrets either, I really like Svelte and tried to convert some data visualization apps with it but couldn't win mindshare at the time in these companies.

I haven't look into too much, but what made react easy to adopt was that Facebook would put out codemods to help migration during major transitions. It was easy to justify these version bumps when there was tooling that made these transitions somewhat painless.

[alserio]

If I may, you are a major behind, and not much has changed from 3. 4 to 5 seems that will be more "radical" but right now is still in development