5 ms·
This is a bit like saying that you’ve stopped driving to work and now you only walk. That’s great for you if your home is close enough, then of course you shou
by zarzavat 4y ago
This is a bit like saying that you’ve stopped driving to work and now you only walk.
That’s great for you if your home is close enough, then of course you should have been walking. But it’s not exactly generally applicable advice.
The whole point of React is to create interactive UIs, that’s why it’s called “react”. And you can’t do that with a templating system.
- p5v 4y agoJust wait till you hear about HTMX: https://htmx.org/ https://htmx.org/
- MuffinFlavored 4y ago> No complicated build systems or web pack or dependency management system. I love statements like this. It's as if things are just complicated for the fun of it, not because they need to be/they solve complex problems.
- kupopuffs 4y agoThe complex problem of having great code turn compiled into shitty-ish code that some browsers support
- irrational 4y agoI’m not sure the complex problems these tools were originally created for still exist. For example, do you really need to support old browsers? If not, you probably don’t need a transpiler anymore.
- dimmke 4y agoWell, webpack has been replaced by vite (for those who pay attention to front-end trendfuckery) which is much simpler than Webpack and Babel is eliminated. We are still not quite at the point where it’s practical to not have a module bundler. Handling things like imports etc is still necessary. But we are moving away from React. Things are slowly going back to sanity. SvelteKit is an excellent step in this direction IMO.
- squeaky-clean 4y agoIf you're using Typescript you need one.
- mirekrusin 4y agoUnless you’re using it just for type checking js/jsdoc. Flow is much better in this area.
- robertoandred 4y agoDo you think there haven't been any new JS features in the past ten years?
- Joeri 4y agoYou’d be surprised how widespread support for newer javascript functionality is now that all browsers are evergreen.
- nightfly 4y agoWhen you have a problem that can be solved with a hammer and nails you don't break out the TIG welder
- selfmodruntime 4y agoYou also don‘t endlessly build strawmen on HN about people using TIG welders where a hammer would suffice
- petilon 4y agoWould you say Amazon.com has an interactive UI?
- irrational 4y agoProduct pages? No. Search page? Eh… maybe. Checkout page? Probably.
- squeaky-clean 4y agoTheir customer support pages with built-in live chat do. And I'm assuming we're excluding aws.amazon.com with realtime graphs and viewable log streams.
- nine_k 4y agoThe usual problem is that people often pick an SPA tool for a job that a CGI script can handle. The fashion made "web UI" and "react" associated too strongly. Much simpler tools can work if you allow for less fluid interfaces, and this may be a non-issues for a tool running on a LAN.
- otabdeveloper4 4y ago> less fluid We're never replacing our old-style PHP internal tools, because according to business users it's "instantaneous", and any attempts to use a more SPA approach cause complaints about "sluggishness".
- eastbound 4y agoOnce the CGI page loads, all info is in there. React requires 1 request for the basic HTML, (1 request for the JS but it’s generally cached) and 1 request for the data from the REST API. It’s double the time to load a page. React apps constantly have gray placeholders waiting for data to finish loading. Contrary to initial experiments, progressive rendering is recorded by the brain as a bad experience.
- terandle 4y agoReact's new server components (only in next 13 at the moment, coming soon to other framework) addresses this problem. Of course react and node both have performance work they need to do also.
- zarzavat 4y agoReact is simply a library that renders your UI to the DOM. It doesn’t have any opinions on how your data is fetched, or how many roundtrips it takes. That’s an orthogonal concern. People have been using XMLHTTPRequest with CGI since the 00s, way before React was a twinkle in Zuck’s retinal sensors. You can send your initial data for React with the HTML response if you want to eliminate the extra round trip on startup. Depending on the geographical distribution of your users it may or may not be worth it.
- uranusjr 4y agoI mean, there’s been outcries how the US is overly car-dependent and driving should be a choice not a requirement etc. The parent is onto something if you go with this analogy.