svelte-it-will-scale VS npmgraph.an

Compiled code logic redundancy. Some readers may worry that if the complexity of the business logic, resulting in a straight line increase in the size of the code file after compilation, whether it will lead to a certain degree of performance degradation?Github on the relevant developers for this problem to analyze svelte-it-will-scale:

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.

Sure, performance (bundle size), performance/predictability, simplicity (blog post)

Finding Svelte's Inflection Point

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 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.

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.

The problem with those packages that are "all inclusive" is that you end up depending on a very large number of third party packages, even if your use case probably doesn't require it

https://npm.anvaka.com/#/view/2d/better-auth

It's referring to all transitive dependencies - not just direct dependencies. More like this: https://npm.anvaka.com/#/view/2d/vue

All the points listed above are multiplied, to some extent, by the number of dependencies in the entire dependency tree of the project. A great tool to check the complete dependency tree: https://npm.anvaka.com

A colleague of mine just told everyone that vue.js is simply bloat, other frameworks are better and he doesn't want to work with vue.js. As "source" he sent this following link: https://npm.anvaka.com/#/view/2d/vue and told us to compare it to @angular/core and react. I love vue and obviously know that it isn't bloat, but I don't know how to argue my point.

I saw this yest and it’s kind of cool to visualize all the dependencies of a package. Hope it helps https://npm.anvaka.com/