3 ms·
Except the cool new thing is still React, and we're all still here. Folks are building products with great UX -> Clients use these products, want the same thin
by rozenmd 4y ago
Except the cool new thing is still React, and we're all still here.
Folks are building products with great UX -> Clients use these products, want the same thing in their products -> Demand for frontend increases, repeat.
- pcthrowaway 4y agoReact is still in, but it's definitely not the "cool new thing" now. Svelte and Solidjs seem to be the "cool new things" now on the front-end
- deleted 4y ago[deleted]
- siquick 4y agoYou’d be hard pushed to find any production applications of any scale using either Svelte or Solid.
- pcthrowaway 4y agoThere are lots of large production applications using Svelte
- dt2m 4y agoThere's no question that it's still highly in demand, but as a user I despise React apps. Not that there's anything wrong with the technology - well-written React with minimal dependencies can provide a great and responsive UX. In practise this rarely is the case. I have yet to use a React app that consistently respects Cmd+click as my intent to open something in a new tab, has sub-100ms draw times for any UI action, and doesn't need to load multiple megabytes of JS to bog down my CPU for basic CRUD stuff.
- arvinsim 4y agoYou are basically asking for a native OS app, which the web cannot match. But users demand them anyway on the web so here were are.
- dt2m 4y agoOf course I would prefer a native app, but I don't think it is unreasonable of me to expect a web app to: - Respect the UI conventions of web browsers and not override standard behavior - Respond immediately to user input - Not take up hundreds of megabytes of RAM I have yet to use a React app that doesn't immediately "feel" like it's using React. There's some weird added latency that I can't really describe, but I don't feel it on Angular apps.