281–289 of 289 posts
Earlier quoted context omitted.
Plain JS -> Angular -> React -> Vue -> Svelte What a long strange trip it's been
Don't forget jQuery! :) It feels like it was Plain JS -> jQuuuuuuuuuuuuueeeeeeeeerry -> Angular -> React -> Vue -> Svelte
Earlier quoted context omitted.
and JSX somehow gets your blessing? let he who is without sin…
I'm not the one who wrote above but I see JSX as having fewer magic things than all other template languages I've seen. Take a look at Angular to see some complicated syntaxes examples. Vue and Svelte are better but, IMHO, not as easy as JSX.
Earlier quoted context omitted.
> Vue 3 is great, I highly recommend reacty-folks or frontend devs try it. We wanted the larger ecosystem (and boo to us for not being brave enough to support the growing vuecosystem). I enjoy Vue 3 and I don't enjoy React, but like you this is the reason I keep heading back to React. From tldraw [1] to react-flow [2] to the superb AtlasKit [3] to form builders & validators, the React ecosystem contains great stuff t…
Have you seen https://vueflow.dev/
Earlier quoted context omitted.
> React + TypeScript [...] anecdote I agree that that combination it is very ceremonial. We now doing new projects in Elm as the JS/TS ecosystem simply does not cut it for me.
Wise choice, but it brings along with it the curse of Plato’s Cave.
Earlier quoted context omitted.
Plain JS -> Angular -> React -> Vue -> Svelte What a long strange trip it's been
Don't forget jQuery! :) It feels like it was Plain JS -> jQuuuuuuuuuuuuueeeeeeeeerry -> Angular -> React -> Vue -> Svelte
We just did the reverse migration from Svelte to Vue 3.
How did it goes and the experience?
I have written a post clarifying them: https://blog.vuejs.org/posts/on-migration.html
Earlier quoted context omitted.
Excellent observation. This right here is what a senior frontend engineer, that has gone through a couple rewrites and hype cycles, looks like. The fact that they used a popularity contest as justification is laughable: if you have more than 3 years in the field you have experienced the pattern that the new kid on the block, often untested and with smaller mind share, jumps to the top of any "which framework would yo…
Seems like a rewrite for the sake of a rewrite. New frameworks are exciting but if you're building a product you have to realize that's not important to your customers. Sure if you were on PHP, a rewrite to a JS framework would be worth it, because you could deliver features to your customers faster, less bugs, etc. But once you're in the JS ecosystem, it gets much harder to justify a lateral migration like that. Lik…
Has anyone worked on a very large Svelte project yet? I work on a large React app in real life, but have been learning Svelte in my off time - there are some nice aspects like the out of the box state management, the syntax and structure is a bit easier to learn than React, but my intuition is a Svelte project would become unwieldy for a very complex app (React class components that are hundreds of lines long with do…
notable companies now using svelte not just for internal apps but customer facing, critical stuff: huggingface (for everything, including gradio), alaska airlines (entire customer flow), razorpay (payment dialogs), schneider electric (many things), ikea (ecomm experience), riot games (league of legends client), Brave (search page), Square (developer portal), several YC startups, and basically every notable data journ…