←back to thread

Svelte 5 Released

(www.npmjs.com)
390 points begoon | 1 comments | 19 Oct 24 18:38 UTC | HN request time: 0s | source
Show context
stormfather ◴[19 Oct 24 21:12 UTC] No.41890822[source]▶
An interesting datapoint:

I made my first website a few months ago (I'm an ML engineer). I tried in both Svelte and React.

I used Sonnet as a copilot the whole time and expected Svelte to be more difficult because there are orders of magnitude less training data on it.

To the contrary! The LLM tied itself in knots very quickly with React but mostly did ok with Svelte/Sveltekit. Also, the Svelte stuff it makes is usually snappier. However it does have a wider range of UI widgets it can grasp with React.

It seems that my opinion that React is horrendously and hideously overcomplicated is at least somewhat objective! Svelte has been quite pleasant.

To any devs out there that have to work with React, you have my sympathies. Compared to Svelte it's just flaming hot putrid garbage.

replies(2): >>41890838 #>>41891113 #
colonelspace ◴[19 Oct 24 22:03 UTC] No.41891113[source]▶
Another interesting datapoint:

Every time I try out something other than React (Vue, Svelte, etc), I have to learn some new syntax, understand the runtime magic, and add a syntax/LSP to my editor. But React is just JS/TS, which is straightforward.

Being disappointed by a library/framework because your LLM of choice can't produce decent code doesn't really tell me very much about the library, other than it's usage is varied.

replies(1): >>41892492 #
1. recursive ◴[20 Oct 24 02:40 UTC] No.41892492[source]▶
The difficulty with react generally isn't the syntax. It's the constraints of hooks and reconciliation. Since mutation is always disallowed (but not by mechanical constraints) data changes are harder to express. You have to remember to keep your effect dependency list synchronized even though the linter can tell you when it's wrong. State continuity depends on the heuristics of the reconciler considering this component instance (and all its parents) to be some particular component instance from a previous render function output.

The syntax is maybe the only good part of react. And I still think the way it uses JSX is not great. Conditionals and .map seem... weird.

But yes, judged from syntax only, react is ok.