Live data from Hacker News

The 49MB web page

thatshubham.com

261–270 of 389 posts

Re: The 49MB web page

#263
post #73

Earlier quoted context omitted.

Same for fancy computers. Dev on a fast one if you like, but test things out on a Chromebook.

Music producers often have some shitty speakers known as grot boxes that they use to make sure their mix will sound as good as it can on consumer audio, not just on their extremely expensive studio monitors. Chromebooks are perfectly analogous. As a side note, today I learned that Grotbox is now an actual brand: https://grotbox.com

Doesn't having a brand for that kinda go against the definition?

Re: The 49MB web page

#264
post #194
post #84

Earlier quoted context omitted.

I’m honestly dumbfounded that these exist In the past some site had light versions, but I haven’t come across one in over 10 years Makes me wonder if this isn’t just some rogue employee maintaining this without anyone else realizing it It’s the light version, but ironically I would happily pay these ad networks a monthly $20 to just serve these lite pages and not track me. They don’t make anywhere close to that from…

a lot of these are internal tools that they just haven't disabled access to for whatever reason. old.reddit still exists for whatever reason.

That's only a matter of time until they kill it. i.reddit.com is already dead.

Re: The 49MB web page

#266

Allowing scripting on websites (in the mid-90s) was a completely wrong decision. And an outrage. Programs are downloaded to my computer and executed without me being able to review them first—or rely on audits by people I trust. That’s completely unacceptable; it’s fundamentally flawed. Of course, you disable scripts on websites. But there are sites that are so broken that they no longer work properly, since the deve…

Disable not just JavaScript, but also CSS. I'm not kidding. Many websites actually contain all the content in HTML but use CSS to hide and then use JavaScript to show it again.

Re: The 49MB web page

#268

Earlier quoted context omitted.

For me personally the most infuriating example of this is the Azure Updates[1] page, which in my job I need to check nearly daily to see what's reaching EoL, what's new, etc... A couple of years ago they redeveloped it as a SPA app. The original server-rendered version of it worked just fine , but it "had" to be made into an interactive client-side monstrosity that loads many times slower for "reasons". It doesn't ev…

GitHub also got infected with this horrible "JS SPA" disease shortly after MS bought them. Now you can't even browse files or view issues without it. If they can't get it right, who can!? Berkshire Hathaway, apparently: https://www.berkshirehathaway.com/ Pure content, not fluff, and even has a small but unobtrusive ad.

Weird, I remember Github as a pioneer of SPAs: in ~2013 you could browse code tree without the page reloading.

Though I agree today's Github is awful slow, JS is required to see issues, …

Re: The 49MB web page

#269
I started on this when project when I was at The New Yorker. I had just manage to convince people to give us space to do web performance optimization - and then we had to drop it quickly to work on AMP. Very frustrating.

This site was created to give developers and pms some ammunition to work on improving load speed

https://webperf.xyz/

Re: The 49MB web page

#270
post #88

Earlier quoted context omitted.

I didn't say anything about their development abilities, what I am pointing to is their professional responsibility. If a doctor is asked by a client to cut off their arm and they say no, and the client fires them, did the doctor err? (No) This doesn't comment on their ability to do surgery.

So just to check, instead of doing something you were told to, that you know is a stupid idea (after telling all concerned it's a dumb idea and being told to go ahead anyway, eg adding a crapton of video to a page), you would just resign, to protect your personal integrity?

no, you offer a technical solution to the problem. Show some videos is the problem. Downloading almost a GB of video content on page load is the (bad) technical solution. There are better ways and as a developer it's part of your job to solve things in a way that makes sense.
Post reply on HN