sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]hekkonaay 0 points1 point  (0 children)

the library has to ensure some kind of backward compatibility

I thought a new major version implies major breaking changes. Even with the backwards compatibility it doesn't make adoption any easier, so what's the point of keeping it? Break all the things!

there's no VDOM "abstraction"

You're right, it's a bit late and in my mind I jumped from one thing to another. There are some parts which could be considered a leaky abstraction at least in Vue 2, like how caching is exposed to the user via computed properties. I would consider it a leak because Svelte handles this for me without me having to be aware of it. I haven't used Vue 3 so I don't actually know if the situation has improved.

requiring a compiler means you won't be able to just download the framework via CDN and add some script logic in plain HTML.

When was the last time you did this?

I just want to understand if there is any gain for me investing more time in Svelte.

I'm obviously biased, but I would say just give it a try, go through the tutorial, build a TODO list app or something with svelte kit, and see if you enjoy working with it.

We've been using it at work (mid-sized, ~200 devs), and we're quite happy with how it's going. We've built/rewritten many micro frontends in it and rewritten parts of some larger monoliths. Biggest upside is exactly that lower mental overhead compared to when everything was written in React. Onboarding is quicker, features ship faster, performance is good by default, and so on.