It's also just actually true that sometimes performance is an ergonomics issue.
@ryanflorence made this point very viscerally years ago to the Ember community in his React talk about how bad performance sometimes makes it hard to say "yes" to features.
-
-
JavaScript got fast in part by turning with() into an aggressive deopt and turning direct eval() into a super-slow operation. The rest of the language was much more optimizable and the results shocked the pundits of the time.
-
JavaScript is in billions of devices, with 4-5 major corporations pouring zillions of dollars into it. I agree there's a ton of low hanging perf fruit here, but who is there to harvest it? And factoring for anti-perf culture..
-
it's like you're trying to solve world hunger on Twitter though.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
