Comment by danielvinson

Comment by danielvinson 11 hours ago

I think this article discounts the reasons behind frontend decisions... priorities are absolutely fast execution time and ease of hiring. There is very, very little reason to care about optimizing frontend performance for a vast majority of apps. Users just don't care. It doesn't make the company more money.

If a framework is easy to use and everyone knows it, it's simply the best choice for 90%+ of teams.

cosmic_cheese 8 hours ago

> There is very, very little reason to care about optimizing frontend performance for a vast majority of apps. Users just don't care. It doesn't make the company more money.

There’s plenty of users who care, but when the competition is also all slow and heavy they don’t get any choice in the matter.

Reply View 3 replies

jonny_eh 8 hours ago

It's usually not the framework that causes apps/sites to be slow.

Reply View | 2 replies
- cosmic_cheese 8 hours ago
  
  Not directly, but when you have devs who only know how to build with the framework and don’t have a grip on what’s going on under the hood or how it all interacts in the browser environment (increasingly common), performance is sure to take a hit.
  
  Reply View | 1 reply
  
  jonny_eh an hour ago
  
  It's not React's fault that people either don't know what they're doing, or don't care enough to make their software performant. This is not a new phenomenon, bad/rushed software has always existed.
  
  Reply View | 0 replies

croes 11 hours ago

The UX for me went downhill the last 5-7 years. I don’t know if it’s react but something changed. Pages load slow or even don’t, strange display errors, slow reaction times etc.

Reply View 1 reply

tracker1 11 hours ago

Too few run output analysis on their bundles or even track bundle sizes. There's a lot of kitchen sink repos, not to mention any number of other bottlenecks between the front end and back end. Worse across split teams for larger apps.

Reply View | 0 replies