svelte-it-will-scale
js-framework-benchmark
svelte-it-will-scale | js-framework-benchmark | |
---|---|---|
7 | 64 | |
171 | 6,484 | |
- | - | |
3.9 | 9.8 | |
over 3 years ago | 4 days ago | |
JavaScript | JavaScript | |
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
svelte-it-will-scale
-
Svelte 4
That N is very large. E.g. here's a page that talks about it: https://github.com/halfnelson/svelte-it-will-scale. I'll note that was done with Svelte 3 and that with Svelte 4 components are at least 10% smaller, so it's actually even better than that. SvelteKit is also very efficient at JS splitting per-route thanks to Vite. It ensures only the JS that is necessary for a page is loaded and you're extremely unlikely to be using anywhere near that many components. Based on the article above, you'd have to have three entire sites worth of components on a single page.
-
Migrating from Vue 2 to Svelte
Sure, performance (bundle size), performance/predictability, simplicity (blog post)
-
What are we trading away when using a UI compiler?
Finding Svelte's Inflection Point
-
My Evaluation of SvelteKit for Full-Stack Web App Development
yes am aware, but also in any realistic scenario, code splitting comes in well before the crossover point where that even remotely comes into question. this has been independently verified twice now:
https://twitter.com/sveltesociety/status/1301168598988107776...
https://svelte-scaling.acmion.com/
https://github.com/halfnelson/svelte-it-will-scale
sveltekit has further opportunities for whole-app optimization but honestly given this research i lost interest bc its more than good enough
-
Svelte generates a LOT of JS output code. How is it not adding framework like functionality in runtime?
Svelte lowers the initial size of your app, however the incremental cost of each component creates an inflection point, where the added size of each component exceeds the size of a pre-bundled framework. What actually matters is where this inflection point is. This experiment actually evaluates that https://github.com/halfnelson/svelte-it-will-scale. Essentially, you would need a project equivalent to four times the size of the svelte.dev website to reach this point.
-
Server Rendering in JavaScript: Optimizing for Size
Naturally, the first thing I want to do is put these to the test, but it would be anecdotal at best. The first thing that came to mind was the comparison of Svelte Component Scaling compared to React. Some sort of test to see how much difference a small library that ignored all this compared to a large library that didn't.
- Svelte beats react for developer satisfaction in 2020
js-framework-benchmark
-
Popularity is not Efficiency: Solid.js vs React.js
JavaScript benchmarks are instruments for measuring the speed and effectiveness with which a JavaScript engine—such as the ones found in web browsers—can complete particular tasks. Benchmarks are used by developers and browser vendors to evaluate various engines, find places in the code where improvements are needed, and make sure JavaScript standards are being followed.
-
Use any web browser as GUI, with Zig in the back end and HTML5 in the front end
Strange then that frameworks advertise how fast they are at rendering, mutating, and creating objects in the DOM, and one of the main JS benchmarks everyone likes to measure their performance by is literally a benchmark about DOM manipulation: https://github.com/krausest/js-framework-benchmark
Oh wait. It's not strange. Because state manipulation is a largely solved problem, and even the least performant state manipulation is blazingly fast. However, presenting components in the browser's DOM is tens of magnitudes of orders less performant than anything you can throw at state manipulation.
And every single framework is busy solving one single problem: how do we touch the DOM as little as possible?
- JavaScript-Framework-Benchmark
- GitHub - krausest/js-framework-benchmark: A comparison of the performance of a few popular javascript frameworks
- JavaScript Framework Benchmark
- Vue 3 now outperforms Svelte and React
-
Vue 3 is currently performing better than Svelte and React
It literally says at the bottom "Data from https://krausest.github.io/js-framework-benchmark/"
- Cample.js benchmark reactivity without VDOM
- Rust é uma linguagem que embora tenha uma curva de conhecimento considerável, entrega vários benefícios como segurança e produtividade, reduzindo consideravelmente a verbosidade
-
Imperative - 1.5kb React alternative using Generators
The standard benchmark for js frameworks would be best: https://github.com/krausest/js-framework-benchmark
What are some alternatives?
svelte-kit-koa-boilerplate - This is a boilerplate for svelte-kit and koa.
mikado - Mikado is the webs fastest template library for building user interfaces.
svelte-error-boundary - Error Boundaries for Svelte
sycamore - A library for creating reactive web apps in Rust and WebAssembly
svelte-headlessui - Unofficial Svelte port of the Headless UI component library
yew - Rust / Wasm framework for creating reliable and efficient web applications
solid - A declarative, efficient, and flexible JavaScript library for building user interfaces. [Moved to: https://github.com/solidui/solid]
imba - 🐤 The friendly full-stack language
carbon-components-sv
solid - A declarative, efficient, and flexible JavaScript library for building user interfaces.
sveltestrap - Bootstrap 4 & 5 components for Svelte
Svelte - Cybernetically enhanced web apps