Blazor is popular? First time I hear this. Also the article is commenting on this other article from 2022 which is severely outdated by now. https://journals.riverpublishers.com/index.php/JWE/article/v...
Svelte’s characteristics that likely contribute most to improved performance
61–70 of 205 posts
Re: Svelte’s characteristics that likely contribute most to improved performance
#62Earlier quoted context omitted.
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.
It really isn't - a ui framework should be able to properly handle backend latency and provide a great experience while waiting for a backend response with no flicker while not locking the entire ui. It's just way harder to set up good benchmarks for this.
Re: Svelte’s characteristics that likely contribute most to improved performance
#63Every Svelte enthusiast I have spoken to tends to lean towards the esoteric Elm and other such technologies. They don’t really understand that software isn’t about “my framework can render 1000 elements 500ms faster” but rather my organization of hundreds or thousands of front end engineers (mix of employees and contractors both of whom usually don’t give a fuck) across the WORLD need to be able to work together on a…
if they had stayed on their origin basis of making web apps fast with interop n ease of use the you wouldn't have the rune nonsense.
Re: Svelte’s characteristics that likely contribute most to improved performance
#64Earlier quoted context omitted.
ReactJS is pretty consistent since last 5 years and probably won't be changing for next 5 years.
But how many use _just_ React now? There is a whole stack that 90% of YC companies use: Node, pnpm, Next, React, doing SSR by default. Idk about it all. Most of the time when I ask why they do SSR they can't tell me a valid reason. Their bundle sizes are so big for what the apps do.
Re: Svelte’s characteristics that likely contribute most to improved performance
#65Earlier quoted context omitted.
Didn't React 19 introduce a compiler in an attempt to provide auto-memoization? That feels pretty substantial.
The fact we got to a point of auto-memoization on every reactive function is crazy to me. How is that not prematurely optimizing? I already saw people doing useMemo on shit that shouldn't be getting called repeatedly with the same value. So maybe it is better to let a compiler decide, although I am curious how it knows. EDIT: if its pure (not reactive to any other variable but other variables may react to it) they wi…
Re: Svelte’s characteristics that likely contribute most to improved performance
#66Earlier quoted context omitted.
ReactJS is pretty consistent since last 5 years and probably won't be changing for next 5 years.
But how many use _just_ React now? There is a whole stack that 90% of YC companies use: Node, pnpm, Next, React, doing SSR by default. Idk about it all. Most of the time when I ask why they do SSR they can't tell me a valid reason. Their bundle sizes are so big for what the apps do.
Isn't it mainly about playing nice with crawlers? SEO and the like?
(that was my understanding but I'm a backend dev).
Re: Svelte’s characteristics that likely contribute most to improved performance
#67Re: Svelte’s characteristics that likely contribute most to improved performance
#68The fact this is already outdated by more recent Svelte releases which changed things drastically is exactly my problem with the modern JS space. So fast moving and most of it is still doing JQuery like reactivity. I am probably just not smart enough to get it, but it reminds me of the constant seemingly pointless rewrites I see in companies. Figure out what works and keep it, is that so hard? Why can other languages…
Re: Svelte’s characteristics that likely contribute most to improved performance
#69Earlier quoted context omitted.
But how many use _just_ React now? There is a whole stack that 90% of YC companies use: Node, pnpm, Next, React, doing SSR by default. Idk about it all. Most of the time when I ask why they do SSR they can't tell me a valid reason. Their bundle sizes are so big for what the apps do.
I've used plain react for a few things in the past few years. I strongly prefer it to next/nuxt/all this other stuff. Preact and an understanding of best practices can make it fairly performant with a more or less drop-in replacement if you're willing to sacrifice compatibility with absolutely all the ecosystem. I still prefer svelte but it's less mature and universally-known. React is still a pretty good choice if y…
I know svelte/sveltekit and would want to contribute to svelte apps (a good reminder that I should)
But there are some projects that I really really want to contribute to / heck even port to sveltekit like cinny and hedgedoc and the likes and so I almost feel pressured by the system to learn react so that I can finally feel confident enough to understand their repositories as they scare me right now...
Cinny:https://github.com/cinnyapp/cinny Hedgedoc:https://github.com/hedgedoc/hedgedoc
Re: Svelte’s characteristics that likely contribute most to improved performance
#70Earlier quoted context omitted.
Javascript is not a language that is good for making basic comprehensive abstractions in. Typescript is not a language that is good for making basic comprehensive abstractions in. JSX is not a language that is good for making basic comprehensive abstractions in.
This is quite a large set of things to hand wave away with no additional justification. Makes it sound more like personal bias than meaningful insight