[deleted]
Svelte’s characteristics that likely contribute most to improved performance
11–20 of 205 posts
Re: Svelte’s characteristics that likely contribute most to improved performance
#12I'm so sick of these performance benchmarks. I understand it's easy to spin them up to show that one framework is faster than another, but in general all these frameworks are fast enough for 99.9% of use cases.
Where frameworks lack today, in my opinion, are in providing the right tools further optimize the UX of interacting with web sites. It's a constant struggle of loading spinners and flicker and loss of scroll positions.
The only framework I see that actually tries to resolve these very hard problems is React, through their work on new asynchronous primitives like startTransition. Yes, they are currently hard to understand how to properly use, but I so wish the discourse would be around how to best resolve these actual UX issues than who can create 50M divs the fastest.
Re: Svelte’s characteristics that likely contribute most to improved performance
#13I'm no longer a fan of using any front-end libraries at all en lieu of just using standard event listeners and web components, but in their defense, by the time that you're creating or updating that many elements, most developers are backing out of the framework anyway.
It's the primary reason virtual table libraries exist.
Re: Svelte’s characteristics that likely contribute most to improved performance
#14It's a bit sad that this is using Svelte 3 instead of Svelte 5, which changed its reactivity model to signals!
Re: Svelte’s characteristics that likely contribute most to improved performance
#15Did Svelte gain the adoption like React and Vue ? I am not sure how mature the ecosystem is. I am always wary of using things in production that have not gained significant adoption.
Re: Svelte’s characteristics that likely contribute most to improved performance
#16I'm so sick of these performance benchmarks. I understand it's easy to spin them up to show that one framework is faster than another, but in general all these frameworks are fast enough for 99.9% of use cases. Where frameworks lack today, in my opinion, are in providing the right tools further optimize the UX of interacting with web sites. It's a constant struggle of loading spinners and flicker and loss of scroll p…
Most of that latency is coming from back ends across most major sites, anyway, so it's the wrong place to test.
As an addition to the general commentary here, "The Toilet Paper" is an unfortunate choice of label for this article, and maybe also indicative of the quality of the writing.
Re: Svelte’s characteristics that likely contribute most to improved performance
#17Re: Svelte’s characteristics that likely contribute most to improved performance
#18I love Svelte. When I first used it, it was like using a framework for the first time: Wow, everything is namespaced to the component, even CSS! Wow, just putting $ in front makes it update automatically! etc, etc
Re: Svelte’s characteristics that likely contribute most to improved performance
#19> Because WebAssembly modules lack direct access to the DOM, they rely on an additional JavaScript interoperability layer, which can introduce extra overhead.
Blazor is slow for other reasons. You can make wasm web frameworks fast (see leptos and dioxus). It can be as fast as vanilla js. Sledgehammer on this benchmark is wasm: https://krausest.github.io/js-framework-benchmark/2023/table...
Re: Svelte’s characteristics that likely contribute most to improved performance
#20I'm so sick of these performance benchmarks. I understand it's easy to spin them up to show that one framework is faster than another, but in general all these frameworks are fast enough for 99.9% of use cases. Where frameworks lack today, in my opinion, are in providing the right tools further optimize the UX of interacting with web sites. It's a constant struggle of loading spinners and flicker and loss of scroll p…
Vue has great tools for a lot of this: https://vuejs.org/guide/built-ins/transition