Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

react.dev

And for an example that does it better, legacy.reactjs.org :)

When I saw it I wondered how they managed to drop the ball so hard and how much they paid for it. All they needed is to expand and slightly restructure the docs, but apparently someone sold them a complete redesign that just made the whole docs way less usable (a11y aside, can't speak for that).



sort by: page size:

I've seen those React projects get rewritten.

Credit to the React team. The docs prior to this were poor - I believe the team admitted this.

From the style of writing, to the style of site, I can tell a lot of effort was put into this. Will check out react this weekend - it's been a couple of years (we've been using svelte)


Yeah, the current docs don’t do a great job - I’ve felt like I need to write a really use-case tailored migration guide for my teammates who didn’t pick it up easily by osmosis. Luckily it looks like the React team is hard at work on a new set of docs that does a better job!

https://beta.reactjs.org/


This came out as part of the new React docs site at React.dev, which was launched earlier this year. (There's been a lot of debate about that within the React community since it happened.)

It was built in React.

Cool, so it's React but presumably they've stripped out many of the things that make React enjoyable to use in order to satisfy some arbitrary file size metric. Why isn't this library 1kb, like LatestHotFramework.js?

It's not clear to me what ended up happening. Did they start a rewrite from scratch in React?

I’m sure this is really good, but one of the best things about React is that I don’t know anything at all about its source. Maybe it explains the build system? I was thrown by the import rewrites.

Genuinely confused why someone would reach for React in a 2022 rewrite scenario.

It is on a bad path in terms of integrating with the web platform and doesn’t seem to have any clear signs to resolving that technical debt.


React was originally called Node.PHP or something similar, if I recall correctly!

Oh thats why the dev build of React was there in the page. Makes sense!

The last product we worked on has a larger React file with the fraction of the functionality. Very well done!

React was developed by Facebook. I don't think they did it for small components on otherwise static sites.

They also have been weirdly money focused. Such as moving the react router package to an org called react training. The quintessential routing library of react being sold like that left a bad taste in my mouth. Combined with reacts incredibly poor api, it turned me off react forever. Svelte and vue are both much better.

The thing is, they have bloated out the library quite a bit. One of their early selling points was how much smaller the React library was than Angular/Ember. Now the size of react.min.js has ballooned up to 145.4kb, which is only 10kb short of Angular, and with addons it's even bigger.

As someone who focuses heavily on small page size, that's a pretty harsh regression. Especially when compared to all the other VDom frameworks like Riot/Mithril/Cycle which are all much much smaller and achieve about as much (in my opinion).


Did you read the article or just the word "React"? They're incrementally migrating, not fully rewriting the application.

I didn't mean React is legacy. You can't replace a React app with HTMX in general. I just meant within my project. Those parts are now unmaintained and will be replaced when they break or if we need to change them.

I didn't know React was born by taking another library and removing all the polish and most features from it and then publishing it with almost the same name.

That is create-react-app not react itself but I agree webdev has reached a point of schizophrenia regarding dependencies and performance.
next

Legal | privacy