Google+ had promise in that the many problems of the other platforms could be curtailed with tooling to make your social experience effectively local (not necessarily geographically).

Just close the tabs and never open LinkedIn again.

Does anyone else have the feeling they run into this sort of thing more often of late? Simple pages with just text on it that take gigabytes (AWS), or pages that look simple but it takes your browser everything it has to render it at what looks like 22 fps? (Reddit's new UI and various blogs I've come across.) Or the page runs smoothly but your CPU lifts off while the tab is in the foreground? (e.g. DeepL's translator)

Every time I wonder if they had an LLM try to get some new feature or bugfix to work and it made poor choices performance-wise, but it completes unit tests so the LLM thinks it's done and also visually looks good on their epic developer machines

Out of all places to doomscroll, why choose the one that feels like an episode of Severance?

In fact it's one of my major sources of unsatisfied curiousity is for someone to show a breakdown of a memory dump of a browser, to see, what happens to those gigabytes of memory consumed.

I have heard an explanation that browsers just use free ram, because unused ram is wasted, but that feels flimsy to me. It's not the browsers job to hog ram on the off chance it might need it, just ask the OS when you actually do.

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.

https://news.ycombinator.com/item?id=46904361

May be its time for browser vendors to show the consumption (right now they show memory usage) by features i.e background service, websockets, etc.,

With option to disable background service workers.

Can we talk about how it's possible that any application short of video editing can require so much RAM?

In fact, I've done video editing on computers with 1GiB of RAM back in 2004 and it worked fine, (for the 1024x768 resolution which was en vogue at the time)..

Is linkedin doing something complex? Is there a reason that it requires more resources than my entire computer from 20 years ago, or my entire operating system, text editor and compiler today?

Why not?

other avenues - local slack channels.

linkedIn - good for initial connection with strangers you don't know and might find valuable

linkedIn - good for keeping tabs on companies or new startups

I only open LinkedIn... very rarely. When done, I just close it.

Don't scroll. Don't read stories. Don't do anything except message recruiters. Get them into email or a phone call. That's it. Fuck LinkedIn.

Skin in the game. Yes, it's full of fluffy sounding things, but with a little patience and reading between lines, it's extremely valuable and here's why:

Overwhelmingly most of the time -- when someone posts anything there -- it has the potential to directly quickly improve, or more importantly destroy, their own LIVELIHOOD. It feels like the opposite, but making the choice to post there is a huge risk.

Now, that might come with fluff, of course -- but in a way you could reasonably argue it is the REALEST social media site of them all.

The bigger problem is that browsers these days are not very resource efficient because the programmers behind them have powerful top-of-the-line computers that hide all the inefficiencies (or at the very least, computers significantly more powerful than what their users use). This is compounded by the web developers of most websites also using similarly powerful computers for their development, which hides all of the inefficiencies in the website code. This leads to the clusterfuck of LinkedIn using up 2.4GB of RAM across two tabs (though on my computer 2 tabs only uses up about 600 MB even after a few minutes of scrolling).

It turns out that focusing on developer productivity to the exclusion of the user experience has huge negative externalities. Who would have known? (Answer: Literally everybody who was a programmer before the developer-first mentality took over tech.)

The solution: make browser and website developers use slower and less powerful computers than their average user/visitor will use. The performance issues would be identified and addressed immediately.

  www.linkedin.com##div[data-testid="mainFeed"]:matches-path(/feed)

I had to use it this very morning (yes, that's a new low) and met two errors in two pages. Asked Claude about those bugs, and it made fun of me because they were well known bugs. Even for AIs LinkedIn website is slop apparently.

This HN post to collectively vent some frustration comes in a timely fashion.

(For the record: the first bug was "another admin is already editing this page" making it impossible to edit a business page translations, and the next one was wrong people count when associating personnal profiles to business ones).

No joke, app constantly shows stale posts and stories,,almost like their devs do not understand what the limits to MVVM are for state....rookie mistake