As much as you all dislike LinkedIn and the cringy posts, keep in mind that for certain parts of the market it is >the< main professional forum. It is where your investors live, and their capital providers live. So, play nice, yeah?
LinkedIn uses 2.4 GB RAM across two tabs
191–200 of 481 posts
Re: LinkedIn uses 2.4 GB RAM across two tabs
#192Let's be real, LinkedIn is full of LinkedIn Lunatics but pretty much all mainstream social media is pretty shit. They're just different flavors of shit. LinkedIn: bad. Facebook: bad. Twitter: I literally think it contributed to the collapse of discourse and rise of shallow thought / rejection of expertise. I'm not going to list more because the theme is, you guessed it, they're bad. Google+ had promise in that the ma…
Re: LinkedIn uses 2.4 GB RAM across two tabs
#193I don't understand who uses that network anymore. Everytime I login it's all ai generated stories next to ai generated flavor images of people sounding like a parody of themselves ("what taking my kids to school taught me about business scaling"). Out of all places to doomscroll, why choose the one that feels like an episode of Severance?
I doubt many people go to LinkedIn for the cringey and obnoxious feed. It's more write-only than anything. Almost everything about LinkedIn is miserable, not just the feed, and we need a much better competitor that people actually use. One of the challenges to making it much better will be the same problem that most 'social media' apps/sites have: some of the awful is institutionalized and automated, and will go wher…
Recently, a good human recruiter found me an interesting AI startup opportunity. But they were "we're AI-first!" using an AI call scheduling thing instead of Calendly, and it seemed to mess up, so I emailed a quick heads-up about that.
Spent 2 days prepping on their market niche before the call with CTO, and then he no-showed. I got an AI-sounding email from the CTO, after I waited 10 minutes in the call, saying I no-showed, and California-nice offering to reschedule. I replied immediately that I'd been waiting in the call, referenced my earlier heads-up about the AI scheduling, and would continue waiting there in case now was still good. No response...
I wondered whether the CTO wasn't seeing my email due to broken AI managing his inbox, or if he had just blown me off and ghosted after a mess-up on their end that he didn't want to deal with. So I asked the recruiter to make sure employer knew what happened with the AI, and that rescheduling wouldn't just repeat the no-show and ghosting.
No joy after a few days, so I bowed out.
Don't use bad AI; or if you accidentally do, fix the situation when it messes up.
Re: LinkedIn uses 2.4 GB RAM across two tabs
#194Re: LinkedIn uses 2.4 GB RAM across two tabs
#195Let's be real, LinkedIn is full of LinkedIn Lunatics but pretty much all mainstream social media is pretty shit. They're just different flavors of shit. LinkedIn: bad. Facebook: bad. Twitter: I literally think it contributed to the collapse of discourse and rise of shallow thought / rejection of expertise. I'm not going to list more because the theme is, you guessed it, they're bad. Google+ had promise in that the ma…
Social media being bad is partly because of shady business practices, and partly because a lot of people suck (in different ways, at different times, including us). Having said that all of that, have you tried mastodon?
As an aside, I'm not happy with Discord as a platform so I'm working on my own clone with some common identity stuff but with community servers run independently. That is, there are some "federated" identity providers so community servers can agree on identity across servers, then each community server runs its own thing. The trust model is based on the community server - private channels in a community server are not E2E encrypted, you must trust the server. But DMs and DM groups are E2E encrypted and use mutual community servers as relays (with a special class of relay server for people who want to DM but don't have an actual mutual server). I'm having fun with it. Now if only I could figure out why my video has such high latency (even locally!).
Re: LinkedIn uses 2.4 GB RAM across two tabs
#196Back in the ancient days of the web, browsers allowed you to set resource limits (ram, cache, etc) to prevent websites from hogging the limited resources of your desktop system. It's really a shame that all major browsers have since decided that you as a user should have almost no control over how much ram and storage any arbitrary website can consume now.
Re: LinkedIn uses 2.4 GB RAM across two tabs
#197The fact that they hijack scrolling to artificially limit scroll speed is insane to me. Feels like I'm trying to navigate through molasses
Baffles me ui like this exists in 2026.
Re: LinkedIn uses 2.4 GB RAM across two tabs
#198Re: LinkedIn uses 2.4 GB RAM across two tabs
#199Always thought people should be organizing cross industry unions and planning strikes on the platform. Why not?
Re: LinkedIn uses 2.4 GB RAM across two tabs
#200Web developers of HN: how is this possible? What can use 1.2GB RAM for a website? Preloaded all videos?
Checking again it went down to 78meg. Still 78MEG!!! Thats over 1200 Apple IIs, Commodore 64s. I use to run Windows 3.1 for Workgroups, and in it run Microsoft Word, Excel, etc, on machines with 4meg. Now, a simple page of text is taking 78
I get why to some degree. It's highres 32bit display, multi-layered. The screen itself requires 36meg (40bit RGBA, 40bit because it's an HDR display). Each window itself is a texture. If the window is the same size as the screen then that's 36meg. Font Glpyhs are high-res antialias.
Compare that to my Windows 3.1 machine. OSes didn't use textures then and didn't anti-alias. GPUs didn't exist and the screen was 1024x768 or something small like that. Software rendering from fonts that were 1 bit per pixel.
I'm not saying that excuses browsers nor LinkedIn. Rather, if you go add up the basic pieces you'll find that part of the reason these things take lots of memory is because these things take lots of memory.