Live data from Hacker News

Svelte’s characteristics that likely contribute most to improved performance

chuniversiteit.nl

101–110 of 205 posts

Re: Svelte’s characteristics that likely contribute most to improved performance

#101

Earlier quoted context omitted.

Nobody uses plain reactjs anymore.

What do you mean? I use Preact, but I use “plain Preact”.

I think they're talking about React frameworks (aka Next.js).

Re: Svelte’s characteristics that likely contribute most to improved performance

#102

Earlier quoted context omitted.

>Most of the time when I ask why they do SSR they can't tell me a valid reason. Isn't it mainly about playing nice with crawlers? SEO and the like? (that was my understanding but I'm a backend dev).

Do people really build SPAs that are just websites and not ‘apps’?

Sadly, yes. Fortunately, most of them are developers’ toys, but not all.

Re: Svelte’s characteristics that likely contribute most to improved performance

#103

The 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…

The reason the web changes so fast, and there are so many rewrites, is the same reason a puzzle whose pieces don't fit together keeps getting shifted around and restarted. People are looking for a satisfying non-leaky abstraction to build upon and they don't find it with web technologies. They get close, but those last few pieces never quite fit, and we lack the power to reshape the pieces, so we tear out all the pie…

Developers certainly are prey to that impulse, but management tends to want ROI... Rewriting existing apps / services / etc. that work and have been refined over time is usually not a money-maker (unless they can't scale, say). But it is good for PMs and PdMs to say "my team built Z in just two months! (which does do exactly what Y did, but we lost the guy who wrote that...)"

Re: Svelte’s characteristics that likely contribute most to improved performance

#104

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

At least anecdotally I see job listings mostly for React, with some for Vue and Angular, with almost no Svelte. I think I did see one company mention Svelte, so at least someone is building on it, but to a much lesser degree than any of the major players.

Re: Svelte’s characteristics that likely contribute most to improved performance

#105
post #59

Earlier quoted context omitted.

Things change so fast in web dev. Is it so hard to find a pattern that works and stick to it? I think the constant rewrites are honestly _worse_ for dev experience and security. Nobody knows whats standard and docs become outdated so quick a lot of frameworks just have outdated docs or multiple versions that contradict eachother.

Yes, don’t tell me this. I have to rewrite PHP based website because a framework doesn’t work with new PHP anymore. Back compatibility sucks in many software.

It must be a pretty old framework if it doesn't work with new PHP.

Re: Svelte’s characteristics that likely contribute most to improved performance

#107
I'm on a project now that requires using Svelte in an enterprise setting. I've used all the big 3 (Angular, React, Vue) and then some (Ember, AngularJS) and I can say without a doubt, Svelte is my least favorite of them all by far. To say it has encouraged designing an unreadable mess in the code-base is an understatement. It seems to have taken the worst aspects of the big 3 and ran with it. I'm utterly confused why people enjoy this wild west hodgepodge of framework mistakes. I'd argue the improved speed is not worth sacrificing readability and lower cognitive load. This is designed for tinkerers and hobbyists. I say this with confidence of nearly 20 years experience building enterprise web applications (including in FAANG): Svelte is another fad library that has no place in a professional setting.

Re: Svelte’s characteristics that likely contribute most to improved performance

#108

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

> I'm no longer a fan of using any front-end libraries at all en lieu of just using standard event listeners and web components You can get away without using frontend frameworks for small and simple projects. However, for large and complex projects you will struggle. For example, try building Google Docs without a frontend library. You will struggle even if you have an army of developers at your disposal. In fact, w…

> You can get away without using frontend frameworks for small and simple projects.

Small and simple projects like checks notes VSCode, Obsidian, Min (browser).

Re: Svelte’s characteristics that likely contribute most to improved performance

#109

I'm on a project now that requires using Svelte in an enterprise setting. I've used all the big 3 (Angular, React, Vue) and then some (Ember, AngularJS) and I can say without a doubt, Svelte is my least favorite of them all by far. To say it has encouraged designing an unreadable mess in the code-base is an understatement. It seems to have taken the worst aspects of the big 3 and ran with it. I'm utterly confused why…

Care to talk in specifics rather than generalities?

Re: Svelte’s characteristics that likely contribute most to improved performance

#110

I'm on a project now that requires using Svelte in an enterprise setting. I've used all the big 3 (Angular, React, Vue) and then some (Ember, AngularJS) and I can say without a doubt, Svelte is my least favorite of them all by far. To say it has encouraged designing an unreadable mess in the code-base is an understatement. It seems to have taken the worst aspects of the big 3 and ran with it. I'm utterly confused why…

lol, I love this take! I honestly have never used Svelt but you hear so much fanboi love for it I assumed it actually was awesome! If Svelt is a hipster scam, that would be hilarious. Anyone else able to corroborate or refute this claim?

I personally like React with just React Router 7 in framework mode (Remix). So simple, so intuitive, just works, paper thing abstractions over stuff everyone already knows how to do. (Next.js OTOH I do not love)

Post reply on HN