Hacker News new | ask | show | jobs
by the__alchemist 729 days ago
When I first learned react and web programming, I was very confused about this! React was advertised as fast! From reading react docs, articles, tutorials etc. There was a concept called "fiber" that was around the corner that would make websites even faster; it had demos where pixels would dance around the screen. I didn't grasp what made it faster, but assumed it was doing some binary magic in the web browser!

I learned more, and ended up writing my own react-like framework in Rust/WASM. (Seed).

Now, I program in HTML, CSS, and JS. If the project triggers a certain complexity threshold, I'll bring in TS.

React advertising itself as fast was a lie.

2 comments

What exactly is a react like framework in wasm? Your wasm is going to end up calling the same dom updating functionality except with the extra IO overhead. I can’t imagine that’s going to perform better. This doesn’t even sound like a good use case for wasm.
It doesn't perform better; it has the same problems.
It was fast! Now it's legacy tech.
>Now it's legacy tech.

Yep. The tide is turning fast toward Vue these days. React died with the departure of Abramov. It's been over 2 years since the last major release, and 19 just screams nonsense "makework" incremental stuff.

I think you need to get out of your bubble, Vue in its current state is significantly less popular than react.

https://www.similartech.com/compare/react-js-vs-vuejs

That doesn't refute what the GP is saying. "Tide is turning" is about a rate of change; that site only presents a snapshot of the current state of things.

Not saying you're wrong, as I have no evidence either way, but a more useful measure to see what's happening would be a plot of the numbers of React and Vue sites over time.

I've heard of Vue but legitimately thought it was an IDE or something.