4 ms·

> all about developer experience and neglected user experience I think this is a mix of good old cargo culting and how hot the dev market is. Small companies d

> all about developer experience and neglected user experience I think this is a mix of good old cargo culting and how hot the dev market is. Small companies don't have the leverage to tell their engineers "no" when they do a bit of resume driven development. React makes sense for many of sites at larger tech companies paying big salaries because many of them are delivering a richer "application" experience. Some engineers blindly follow what "better" (massive air quotes) companies are doing. Others who want to work at these companies want the skills that will make them more hireable and so choose React. Devs who are not in either of these other camps make a small enough group they don't generally get their way.

girvo 5y ago
I’ve worked in React full time for seven years, and the biggest thing I’ve learned is that too many companies choose it when it’s absolutely not the right choice. Plenty of things are basically websites with forms and a dash of interactivity. Building a full single page web app for this is a waste of everyone’s time and their customers CPU cycles, and it’s not even faster to develop most of the time… My current job is a fully fledged web application for a B2B IoT platform, with soft real-time data and huge interactivity. React et al. fit this better, and because we have some control over who and what devices are using it, it’s (frankly, mitigated if you know what you’re doing) overhead isn’t a problem. I love React, I really do. But it’s not the right fit for everything, and I’ve earned a huge amount of money coming in to save projects that are failing due to that incorrect choice.
- nerdponx 5y ago
  I have worked on a project that literally served static text on a page with static links, some embedded media, a bookmark toggle thing, and a hamburger menu, that were heavily using React. The reason I was told was that they wanted the "components" framework to support modularity and reuse. Is there an alternative for that purpose?
  - rtcoms 5y ago
    In Ruby on Rails there is gem called ViewComponent. Create and being used by github. May be something similar should be there for other frameworks too.
  - lobocinza 5y ago
    Static site generators. I recommend Hugo.
  - girvo 5y ago
    Most server-side templating systems (or static site builders that use the same or similar templating tools) allow for easy modularity and reuse, but if they really need that “SPA” type feel then htmx is a brilliant and simple choice to add behaviour without needing to adopt a fully SPA architecture https://htmx.org/ https://htmx.org/

girvo 5y ago

I’ve worked in React full time for seven years, and the biggest thing I’ve learned is that too many companies choose it when it’s absolutely not the right choice. Plenty of things are basically websites with forms and a dash of interactivity. Building a full single page web app for this is a waste of everyone’s time and their customers CPU cycles, and it’s not even faster to develop most of the time… My current job is a fully fledged web application for a B2B IoT platform, with soft real-time data and huge interactivity. React et al. fit this better, and because we have some control over who and what devices are using it, it’s (frankly, mitigated if you know what you’re doing) overhead isn’t a problem. I love React, I really do. But it’s not the right fit for everything, and I’ve earned a huge amount of money coming in to save projects that are failing due to that incorrect choice.

nerdponx 5y ago
I have worked on a project that literally served static text on a page with static links, some embedded media, a bookmark toggle thing, and a hamburger menu, that were heavily using React. The reason I was told was that they wanted the "components" framework to support modularity and reuse. Is there an alternative for that purpose?
- rtcoms 5y ago
  In Ruby on Rails there is gem called ViewComponent. Create and being used by github. May be something similar should be there for other frameworks too.
- lobocinza 5y ago
  Static site generators. I recommend Hugo.
- girvo 5y ago
  Most server-side templating systems (or static site builders that use the same or similar templating tools) allow for easy modularity and reuse, but if they really need that “SPA” type feel then htmx is a brilliant and simple choice to add behaviour without needing to adopt a fully SPA architecture https://htmx.org/ https://htmx.org/