Re:Putting Devs Before Users: How Frameworks Destroyed Web P...
by abraham on Wednesday January 01, 2020 @11:25PM
(#21933033)
The median desktop site is almost 2MB. https://httparchive.org/reports/page-weight
Re:Putting Devs Before Users: How Frameworks Destroyed Web P...
by TheCoelacanth on Thursday January 02, 2020 @11:11AM
(#21936556)
I believe it, but it's not because of what framework they are using. React is only 100k. It's because of writing bloated websites without a concern for performance.
Re:Putting Devs Before Users: How Frameworks Destroyed Web P...
by threeseed on Thursday January 02, 2020 @12:30AM
(#21933239)
That includes resources like images, videos etc.
Javascript is 1/5 i.e. 420KB
Re:Putting Devs Before Users: How Frameworks Destroyed Web P...
by Cyykratahk on Thursday January 02, 2020 @02:03AM
(#21933524)
The linked Medium article is over 3MB, almost 2MB of that being JS.
Re:Putting Devs Before Users: How Frameworks Destroyed Web P...
by viklove on Friday January 03, 2020 @01:09PM
(#21948584)
It's not the UI framework that's adding the bloat, it's a bunch of tracking and fingerprinting scripts. They would still be there even if the UI was server-rendered HTML, because that's Medium's business model!
Although web performance is certainly a problem, the bigger problem with the web in my opinion is actually poor UX. Often when I'm on a website it's very confusing how to figure out how to do basic tasks like finding the search bar. Medium has the most appalling comment system I've ever seen, requiring 3+ clicks/refreshes to read a comment on an article.
Although I agree the web performance is a serious problem, this is a very weak article, and I'm surprised it's on the front page. I guess people will upvote anything that complains about web performance, no matter how poorly reasoned and misplaced the blame is.