Closed mine ages ago, along with most of my social media. No need for it, never was a need for it.

Not only it's huge and slow, but the design is broken (some elements frequently masking others, like the top banner masking half the top menu, or the icons masking the search box), and it's full of errors.

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).

For sure there is more to what they just show

Github hogging cpu when js is turned off

I think it is an accomplishment to bloat a website to a point where the user needs to download 40-100mb per page. Even if I try, I can't find the right JS files to make it that large. How do they even make JS files this big?

As someone pointed out below, the problem is not entirely (or even mostly) LinkedIn. HN, a text-only website, consumes several hundred MB of RAM on his Mac. On Firefox on my Windows computer, each HN tab I have open consumes at least 30 MB of RAM...for pure text...

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.

LinkedIN, showing why Reactive is such a good idea by refusing to use it....

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

Beyond being useful for a quick check on someone’s career history, LinkedIn is mostly full of grifters pretending to be experts in things while the actual experts never post about the subject on LinkedIn.

LinkedIn is full of crap. Unfortunately is the only way to get recruiters visibility.