Comment by wg0

Comment by wg0 11 days ago

This is great. But I went for Svelte. Invested in Svelte and SvelteKit. Wrote a decent sized app (not toy example, pretty feature right, tens of forms and screens if you will) and later I looked back at React.

And I discovered that:

  - React is not that hard if you understand the hooks.

  - React is lightweight too. For my use case at least.

  - React is boring technology at this point which is good.

  - The ecosystem is huge. You cannot have React Query like library and that's just one example.

So I'm sticking to React for next few years especially when the React compiler is already being used inside Facebook and Instagram and released as public beta.

Even React Native supports React compiler and I don't see this support going away rather getting better.

PS Edit: React compiler leaves not much for runes in Svelte or its compiled nature. I don't like Svelte much after runes because it feels like you're not writing Javascript rather a notation that looks like Javascript. Post React compiler, much of the hooks hell is not needed in complex scenarios.

brulard 11 days ago

TanStack Query (formerly known as React Query) is absolutely compatible with Svelte. https://tanstack.com/query/latest

I work with react for a decade now, and with Svelte for past 3 years. Svelte is obviously a newer generation of framework, and works for me a lot better than React. But I agree there are some rough edges, mostly around the ecosystem

Reply View 1 reply

wg0 11 days ago

No, the support is quit limited not as many features are supported.

Reply View | 0 replies

pier25 11 days ago

Svelte is definitely much less verbose and requires less code. Performance is also way better but it might not matter for many use cases.

The drawback is that since Svelte is really a language[1] you now need a compiler and custom dev tools to make it all work. This requires some serious effort to maintain and evolve.

I love Svelte and have been using it almost daily for years... but the team really needs more resources to accomplish their vision and maintain it for the foreseeable future. It's amazing that huge companies like Apple are adopting Svelte (eg: Apple Music) and not investing in it.

[1] https://gist.github.com/Rich-Harris/0f910048478c2a6505d1c321...

Reply View 0 replies

iammrpayments 11 days ago

I transitioned to svelte and I’m finding it around 3x to 2x times less complex than React

Reply View 0 replies

newswangerd 11 days ago

I learned React back in the class component days. I recently picked it back up and found functional components and hooks to be absolutely baffling. Does anyone know why they went down this route?

Reply View 2 replies

wg0 11 days ago

Trust me, the function based components are way too simpler. Just a function that returns HTML. That's it. compose your UI as those functions. These functions can take arguments to customise their output (rendered HTML) as arguments (called props) or can call special functions from React (called hooks) such as asking the React to "remember" a value for you (state) or cache something for you (useMemo) so as to not compute it every time or trigger rendering if value of certain variables change (useEffect) or at the component start (useEffect with no dependencies mentioned) and that's all the React that you need to know for I would say your 95% of the needs.
React compiler (already used for Facebook and Instragram code base) further renders the use of certain hooks unncessary thus making React a lot more simpler.

Reply View | 0 replies
jfcisco 11 days ago

Hooks require less boilerplate to set up and reuse stateful logic across components
If you havent watched it yet, the talk that introduced hooks explains much better than I can: https://youtu.be/dpw9EHDh2bM

Reply View | 0 replies