Comment by denysvitali
17 hours ago
A probe collecting data in space takes <70 kB of memory. I fail to see how this statement should make me feel happy
17 hours ago
A probe collecting data in space takes <70 kB of memory. I fail to see how this statement should make me feel happy
Space is mostly empty there is not much interesting stuff to collect and who’s going to buy that data
LinkedIn on the other hand has user behavior, computer details etc. that’s a lot of interesting data.
>Space is mostly empty
Yes, but Space is big. Really big. You just won't believe how vastly, hugely, mind-bogglingly big it is. I mean, you may think it's a long way down the road to the chemist's, but that's just peanuts to space.
Exactly and people on LinkedIn think they are smarter than everyone and definitely smarter than dolphins, because what dolphins do? They muck in the water all day having good time whereas humans built important profiles on LinkedIn having good time berating each other.
As someone was pointing out in a thread the other day about memory usage, a lot is fonts and images.
EDIT: Just mind boggling to get d/v'ed for pointing out voyager doesn't have to render fonts or images...
How much? You typically don't want more than a few different fonts on a given document. And neither fonts nor web images should be bigger than hundreds of kilobytes. How do we get to gigs?
I don't see mention of this in the discussion, so I will add: I think people also don't close tabs. And probably these LI tabs have been up for a long time. Maybe weeks or months.
I completely exit my web browser(s) at least 1x per day, and use bookmarks to get back to pages I need. As a result, I don't have issues with memory leaks or unbounded growth of RAM use. For me, its just the "proper" way to use a program like a web browser, but I'm old enough to be from the era that restarting programs and the OS could fix issues. I recognize that most people feel it is unreasonable to quit the browser, pretty much ever.
> How do we get to gigs?
Are you aware of what LinkedIn is? How the app behaves?
While it’s obscene, I am not surprised at all.
2 replies →
>How do we get to gigs?
Microsoft, who has owned LinkedIn since 2016, has recently been making headlines because recently they fired a lot of their engineers and QA staff and are now essentially vibecoding huge chunks of their enterprise.
What's more, Microsoft never paid the really big bucks like the FAANG companies, and so it's more or less an open secret that at the height of the tech hiring frenzy Microsoft had to fight for B-tier engineers that weren't good enough to work at e.g. Apple.
So, it's been 10 years, which is long enough for that trademark Microsoft mediocrity to seep into LinkedIn. And they're probably vibe coding everything. That's how you get to gigs.
3 replies →
Well, and then you have Claude Code which at one point needed 68GB of RAM to run https://x.com/jarredsumner/status/2026497606575398987
:)
Aka poor resources management.
If you have significantly more images loaded in RAM than what fits on your screen, something wrong is going on. (Not counting the filesystem cache here, because it works in a best effort way).
The alternative is that for every glyph you render the entire glyph to the screen using the Bezier curves from the font, and you end up with dogshit performance - like the new windows terminal (not sure if they've fixed it yet).
Caching glyphs is good resource management and with modern screen resolutions, color displays and subpixel-antialiasing you just simply need more than 70KB of RAM.
1 reply →