I don& #39;t usually do this, but it& #39;s about public health and this site is getting a lot of press and HOLY !*#$ WHAT IS WRONG WITH THE REACT COMMUNITY!?:
https://www.webpagetest.org/result/200419_RQ_7d92404e9fc558919d13effd65fde874/">https://www.webpagetest.org/result/20...
https://www.webpagetest.org/result/200419_RQ_7d92404e9fc558919d13effd65fde874/">https://www.webpagetest.org/result/20...
This feels like the right place to invoke @tomskitomski:
https://twitter.com/tomskitomski/status/1241009376653012993
If">https://twitter.com/tomskitom... I had to guess, this probably wasn& #39;t ever tested on anything w/o a "Designed in Cupertino" badge.
https://twitter.com/tomskitomski/status/1241009376653012993
If">https://twitter.com/tomskitom... I had to guess, this probably wasn& #39;t ever tested on anything w/o a "Designed in Cupertino" badge.
It& #39;s *more than 900K of JS* to see the headline data. A screen shot is significantly smaller.
Nothing about this is OK.
Nothing about this is OK.
Once -- just once -- I& #39;d like to see prominent React peeps pitching in to fix these sorts of disasters instead of just excusing them.