> 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.

▲

jonny_eh 21 hours ago | parent [-]

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

▲

cosmic_cheese 21 hours ago | parent [-]

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.

▲

muspimerol 8 hours ago | parent | next [-]

This happens regardless of which framework is used or even if no framework is used. Plenty of web developers do not understand how the browser or JS work at a deep level.

	▲	LegionMammal978 3 hours ago \| parent [-]
		Yeah, it's pretty close to the "Imagine how great the world would be if everyone used Lisp/Haskell/WhateverLang instead of Java/JS everywhere!" take you sometimes see. As if the common developer wouldn't just write in all those languages like they're Java/JS, and keep clear of the advanced macros/type systems/whatever. Even languages or environments that try to "steer the developer into the correct direction" have only really managed it when the new direction is something they already might've chosen to write. Otherwise, you just end up with many square pegs filed down to fit in round holes.

▲

jonny_eh 14 hours ago | parent | prev [-]

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.

	▲	wahnfrieden 32 minutes ago \| parent [-]
		GitHub somehow became instantly slow to this day after they started introducing React but I guess it’s just their devs faults