Live data from Hacker News

Going from React to Vanilla JavaScript

alexbezhan.substack.com

31–36 of 36 posts

Re: Going from React to Vanilla JavaScript

#31

To denigrate so much of modern web technologies in the name of performance, and then use Typescript, over which you have no fine grained control of the performance of the transpiled code, is absolutely laughable.

Ridiculous take. TypeScript turns into JS practically one-to-one. In 5 years I’ve never heard of a performance problem introduced in transpilation.

Re: Going from React to Vanilla JavaScript

#32
post #11

A lot of people don't know how to use react. The author is one of them.

Author here. I've used React Table for this, which has like 20k+ stars on Github. It's slow. Imagine you want to edit a cell in a spreadsheet with 40k rows. You MUST create a new array, otherwise React won't update the DOM.

No you just update the cell. React is extremely fast if you understand how rendering works. Avoid unnecessary rerendering of unchanged data.

Re: Going from React to Vanilla JavaScript

#33
post #6

As someone who got out of the web dev game before reaact, I feel like everyone using react has led to most of the web sites (and mobile apps) feeling slow. My judgy view is that when you see apps that appear to be single page but take noticeable time to load their content - that's react. And as someone who built a spreadsheet app in.. say 2006, you have to go native to get good performance. But I base my observations…

No no. Your observations are correct. The coolness of web hooks prevents anyone from seeing how chaining multiple async operations into a single call chain makes things slow. I know...I know. This is Javascript and the level of abstraction is far beyond the metal I just described. But that's kind of the point here. It's possible to abstract yourself into a performance problem. We've reached peak abstraction.

Re: Going from React to Vanilla JavaScript

#34
post #6

As someone who got out of the web dev game before reaact, I feel like everyone using react has led to most of the web sites (and mobile apps) feeling slow. My judgy view is that when you see apps that appear to be single page but take noticeable time to load their content - that's react. And as someone who built a spreadsheet app in.. say 2006, you have to go native to get good performance. But I base my observations…

You’re missing part of the picture. It also takes a huge time to develop, and requires people with a lot of experience in FE architecture, or you’ll mess up your redux. I wish I were joking.

Yeah, state management has always been a problem on the web.

For others who might not be familiar, redux is a library you can add to your react project to help manage state. There are others but redux seems to be the most popular.

Re: Going from React to Vanilla JavaScript

#35
post #29
post #23

Earlier quoted context omitted.

Have you tried creating your own table in React that supports just your use case? That would've been a fairer comparison un my opinion.

Why should he build his own, you can compare existing things.

Why should he compare a random package that does not fit his use case to his custom solution?
Post reply on HN