I haven't seen that many Svelte websites and most (if not most, all of them) of those websites don't have service workers and other stuff like that. Maybe that's why? What do you think?
jozsefsallai.github.io/insomnia-do... - I made this using Svelte. It might be very fast here, but for larger data, it can get slow. A Vue rewrite is planned, mainly just to see which one would be faster.
My experience with Svelte was... interesting. Rather surreal. If there's one thing I don't really like about Svelte it's exactly that - it removes the niceness of having framework abstractions. It's also really difficult (or maybe impossible) to write actual frontend unit tests for your components (since you're mutating real DOM elements instead of vdom). Sure, there are E2E/integration tests, but it's not the same, especially not in terms of speed.
I wonder why is react still fast even tho it uses virtual dom. At first impression I feel like react website is still faster than svelte website
I haven't seen that many Svelte websites and most (if not most, all of them) of those websites don't have service workers and other stuff like that. Maybe that's why? What do you think?
jozsefsallai.github.io/insomnia-do... - I made this using Svelte. It might be very fast here, but for larger data, it can get slow. A Vue rewrite is planned, mainly just to see which one would be faster.
My experience with Svelte was... interesting. Rather surreal. If there's one thing I don't really like about Svelte it's exactly that - it removes the niceness of having framework abstractions. It's also really difficult (or maybe impossible) to write actual frontend unit tests for your components (since you're mutating real DOM elements instead of vdom). Sure, there are E2E/integration tests, but it's not the same, especially not in terms of speed.
Also, twitter.com/youyuxi/status/1184824...
Yeah. Good point. Would love to see frameworks (similar to nuxt or gatsby) that includes built in testing for svelte.