I was actually a bit curious how much HN uses, since it's probably the lightest site that I frequent.
According to Brave's dev tools, looks like just shy of about 90kb on this comment page as of the time of this writing.
Obviously some of that is going to be CSS rules, a small amount of JS (I think for the upvotes and the comment-collapse), but I don't think anyone here called HN "bloated". Even that one page wouldn't fit on Voyager.
Our comments don't really contradict each other. The page size without any linked documents like an external style sheet grew to 140KB after your comment. But just the text is 30KB.
There is more information in a typical, single page of comments here than there is on the average webpage. And I'd say a far higher signal to noise ratio (though depending on the topic discussed some will disagree).
Nice. Do you just use your 5 as a stationary iPod, or do you dual-carry with a modern device as well? Curious on if you also use it to wi-fi the web on your local LAN periodically too, of it that was just a periodic test to check if HN worked.
I use it around the house to Airplay music to various devices.
A number of things don't work, or work in unexpected ways, mostly because Apple doesn't allow me to log in to iCloud with such an old phone.
I can't control lights with the Home app. But Airplay works fine. The phone doesn't know what a HomePod is, but it shows up with a regular generic speaker icon, like the AirMac I have hooked up to my stereo.
Sometimes I have a few minutes to kill, and I pick it up to look at HN. The New York Times web site starts to work, but the login page doesn't load at all. WSJ blocks me at a "verifying the device" screen. WaPo half works. eBay works some, but no pictures. Ditto for Wikipedia.
There's a lot of things you take for granted on a new phone that you only realize when you're using an old phone. Like you didn't used to be able to quickly scroll an entire web page it's only a screen at a time in iOS 10. You can't grab the scroll bar on the side and move it, either.
And 99.9999% of people don't realize the genius of the camera island. It makes it so much easier to pick up the phone if one end is elevated a bit. With a completely flat phone, you end up dragging/scraping it along the table in order to grip it, which scuffs the surface. And if the table is really smooth, it's surprisingly difficult to lift the phone straight up.
It takes a lot to deliver value at velocity with a team of engineers that couldn't give a damn about the product and just want to get a paycheck, move up the ladder, etc.
LinkedIn is not a fun problem.
The UI, the design, the dark patterns - all of it sucks.
It's a job. Nobody particularly wants to be there. There's nothing sacred about the product. Engineers don't worship it.
It isn't a place you'd take a pay cut for the opportunity to work there.
To be fair. this HN thread useees 40-70 MB of ram in Chrome.
You have to spin it positively: LinkedIn is 350.000 x Voyager.
Any website that uses more memory than Voyager 1 should be considered bloated.
There's almost certainly less than 69KB of useful human-readable information on any given page.
I was actually a bit curious how much HN uses, since it's probably the lightest site that I frequent.
According to Brave's dev tools, looks like just shy of about 90kb on this comment page as of the time of this writing.
Obviously some of that is going to be CSS rules, a small amount of JS (I think for the upvotes and the comment-collapse), but I don't think anyone here called HN "bloated". Even that one page wouldn't fit on Voyager.
That's only HTML but when it is loaded in chromr it is more than 40 MiB.
Huh, fair enough. I was looking at the network console in the browser and it said 89KB.
Almost certainly my fault...sorry!
Our comments don't really contradict each other. The page size without any linked documents like an external style sheet grew to 140KB after your comment. But just the text is 30KB.
This page is only ~30kb. I wonder where the extra ~60kb you're seeing is coming from?
There is more information in a typical, single page of comments here than there is on the average webpage. And I'd say a far higher signal to noise ratio (though depending on the topic discussed some will disagree).
I was actually a bit curious how much HN uses, since it's probably the lightest site that I frequent.
I use an iPhone 5 as an iPod. HN is one of the few web sites that still works with iOS 10.
Nice. Do you just use your 5 as a stationary iPod, or do you dual-carry with a modern device as well? Curious on if you also use it to wi-fi the web on your local LAN periodically too, of it that was just a periodic test to check if HN worked.
I use it around the house to Airplay music to various devices.
A number of things don't work, or work in unexpected ways, mostly because Apple doesn't allow me to log in to iCloud with such an old phone.
I can't control lights with the Home app. But Airplay works fine. The phone doesn't know what a HomePod is, but it shows up with a regular generic speaker icon, like the AirMac I have hooked up to my stereo.
Sometimes I have a few minutes to kill, and I pick it up to look at HN. The New York Times web site starts to work, but the login page doesn't load at all. WSJ blocks me at a "verifying the device" screen. WaPo half works. eBay works some, but no pictures. Ditto for Wikipedia.
There's a lot of things you take for granted on a new phone that you only realize when you're using an old phone. Like you didn't used to be able to quickly scroll an entire web page it's only a screen at a time in iOS 10. You can't grab the scroll bar on the side and move it, either.
And 99.9999% of people don't realize the genius of the camera island. It makes it so much easier to pick up the phone if one end is elevated a bit. With a completely flat phone, you end up dragging/scraping it along the table in order to grip it, which scuffs the surface. And if the table is really smooth, it's surprisingly difficult to lift the phone straight up.
640K is all anybody actually needs
https://news.ycombinator.com/item?id=18120477
Any development team larger than Apollo programming team of 350 is overstaffed.
Any development team larger than Apollo programming team of 350 is overstaffed
We put a man on the moon mostly with pencils and slide rules.
Today we have massive data centers full of "AI" supercomputers, and we get… TikTok?
Takes a lot of resources to track your users rather than just cruising through space
Voyager only needs to track itself. Plus, no ads.
It takes a lot to deliver value at velocity with a team of engineers that couldn't give a damn about the product and just want to get a paycheck, move up the ladder, etc.
LinkedIn is not a fun problem.
The UI, the design, the dark patterns - all of it sucks.
It's a job. Nobody particularly wants to be there. There's nothing sacred about the product. Engineers don't worship it.
It isn't a place you'd take a pay cut for the opportunity to work there.
Hence the bloat.
""just""
Seems that both of these articles are written by LLMs.