LinkedIn uses 2.4 GB RAM across two tabs
A screenshot revealing LinkedIn consuming a staggering 2.4 GB of RAM across two tabs sparked widespread frustration on Hacker News. This eye-popping figure quickly ignited a technical debate on modern web development's bloat and inefficiencies, drawing stark contrasts with historical software's resource frugality. Beyond the tech, the discussion devolved into a collective lament about LinkedIn's content, its user experience, and its paradoxical necessity in the professional world.
The Lowdown
The Hacker News community reacted with a mixture of disbelief and resignation to a post highlighting LinkedIn's exorbitant memory consumption. The original post featured screenshots showing the professional networking site using 2.4 GB of RAM across just two browser tabs, prompting a deep dive into the state of modern web applications and user experience.
- Excessive Resource Use: Commenters were astounded by the sheer volume of RAM consumed, drawing comparisons to resource-frugal software of the past, like Voyager 1's 69 KB memory, and noting that even complex video editing software once ran on less. This led to questions about what precisely accounts for this gigabyte-scale usage, with theories ranging from unoptimized JavaScript frameworks and massive image/font caching to an abundance of trackers and background services.
- Widespread Web Bloat: The discussion quickly expanded beyond LinkedIn to a general critique of web bloat. Many reported similar issues with other major sites like AWS, Reddit's new UI, and even simple text pages, experiencing slow rendering, high CPU usage, and battery drain. The consensus pointed to a lack of performance consideration among developers, often using powerful machines that mask inefficiencies, and a trend towards complex, JavaScript-heavy front-ends.
- LinkedIn's Dual Nature: Despite its technical shortcomings, the community acknowledged LinkedIn's enduring (and often begrudged) utility. While many expressed disdain for its "inspiration-porn" content, AI-generated posts, and poor UX elements like scroll hijacking, it remains a critical platform for job searching, recruiter outreach, and professional networking. Some users highlighted its value for niche fields or for keeping track of colleagues, while others actively block its feed to focus solely on its functional aspects.
- User Control & Performance Culture: Specific complaints about LinkedIn's UI/UX included forced scroll limitations, inconsistent navigation, and frequent errors. There was a strong sentiment that major browsers have stripped users of control over resource limits, allowing websites to become increasingly demanding without consequence, a symptom of a development culture where "nobody gets promoted for improving web app performance."
In conclusion, the post served as a lightning rod for broader frustrations within the developer community regarding web performance, the cost of modern development practices, and the paradoxical necessity of using platforms like LinkedIn despite their glaring flaws. The collective outcry underscored a desire for more resource-efficient and user-centric web experiences.
The Gossip
Bloat Bonanza: The Ponderous Performance Problem
Many users expressed shock and frustration at the immense memory footprint, extending the criticism beyond LinkedIn to other popular sites like AWS and BestBuy. The discussion delved into potential technical culprits such as inefficient JavaScript frameworks (React's re-renders, immutable state management), excessive image/font caching, pervasive trackers, and background services. There was a strong sentiment that modern web development and powerful developer machines have created a culture where performance optimizations are deprioritized, leading to what some called "product brain rot" and a return to "IE-era bloat." Some argued that Chrome's memory management intelligently uses available RAM, but others countered that this still impacts system performance and user control.
LinkedIn's Loveless Labyrinth: Necessity vs. Nonsense
A dominant theme was the community's conflicted relationship with LinkedIn. While almost universally despised for its "inspiration-porn" content, AI-generated fluff, "LinkedIn Lunatics," and irritating UI features like scroll hijacking and broken navigation, it is begrudgingly acknowledged as an unavoidable tool for job searching, recruiter communication, and professional networking. Users described it as a "necessary evil" or a "social network that became socially acceptable to browse at work" yet also a "hellhole." The paradox of its crucial professional utility versus its abysmal user experience and content quality was a central point of contention.
Commanding Control: The Diminished User Domain
A significant undercurrent highlighted the loss of user agency over web experience. Commenters lamented the disappearance of browser-level controls for resource limits (RAM, cache) that were common in "ancient days of the web." This lack of control is seen as enabling websites to hog resources, run background processes, and embed numerous trackers without consequence, ultimately degrading system performance and user privacy. The discussion questioned why browsers, especially those from "ad companies," don't offer more granular control or automatic resource management based on site behavior.