Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

LinkedIn uses 2.4 GB RAM across two tabs

news.ycombinator.com

Post reply on HN
Print view View original

451–460 of 481 posts

Re: LinkedIn uses 2.4 GB RAM across two tabs

#451

Post by krieger_857 »

dijit wrote: post #207

Nearly all the top level comments are about the value of Linkedin at all rather than the technical reasons that 2.4G of RAM for a website is atrocious. 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 l…

I know right? Talk about missing the point. Honestly, I think everyday HN is closer to a reddit comment section.

Re: LinkedIn uses 2.4 GB RAM across two tabs

#452

Post by Induane »

raw_anon_1111 wrote: post #450
ywvcbk wrote: post #445

Earlier quoted context omitted.

Yes, exactly, that's what I said. There is significant overhead but is it the only or the main reason why these apps are so slow and inefficient? It's perfectly easy to write slow and inefficient code in C++ as well...

Exactly how would you write a program in C that could possibly be as bloated as adding an entire browser engine + Javacript runtime?

A highly inefficient render loop. I've seen people commit absolute crimes rendering text in game engines.

Re: LinkedIn uses 2.4 GB RAM across two tabs

#453

Post by jrm4 »

kmijyiyxfbklao wrote: post #275
jrm4 wrote: post #144

[flagged]

Well if that gets us LinkedIn, we should move as far away from that as possible, and not listen to the people who want real names everywhere.

Weirdly, I also agree with this.

Which is today, I think we're past the point of "One social media to rule them all."

There's room for multiples, all serving important purposes. Maybe an ideal LinkedIn (work stuff), an ideal Facebook (people you know), Twitter (big public convos) -- and importantly but perhaps nonexistent, a healthy anonymous or pseudonymous space as well.

Re: LinkedIn uses 2.4 GB RAM across two tabs

#454

Post by mghackerlady »

kombookcha wrote: post #433
mancerayder wrote: post #151

Earlier quoted context omitted.

You had me almost spit out my coffee. That's hilariously on point. My favorite is this: The LinkedIn Renaissance Man. It reads like this: "Visionary, Recruiter, Climber, Marathon Runner, Co-founder, Author. Father." That's the sales guys we charge with finding us jobs. Our past co-workers are all CEOs, CTO's, AI experts, and various flavor of Leonardo da Vinci that surely puts my income and achievements to shame.

One of my favourite LinkedIn cranks is a consultant guy who suggested an addendum to Einstein that "Has the potential to impact the future: E=mc²+AI". Because, so he says, "This equation highlights the potential for AI to unlock new forms of energy, enhance scientific discoveries and revolutionize various fields such as healthcare, transportation and technology". It got a lot of traction with the algorithm due to lot…

Either he doesn't understand mass-energy equivalence or is delusional enough to believe ChatGPT can affect the laws of physics

Re: LinkedIn uses 2.4 GB RAM across two tabs

#455

Post by mghackerlady »

wiseowise wrote: post #424
dijit wrote: post #208

Earlier quoted context omitted.

Goes with the territory of allowing remote code execution arbitrarily and all the time otherwise you won't be able to.. * checks notes * read text on the internet.

> read text on the internet. B—b-it 4K scaling! Reactive design (to read text)! Emojis, reactions, badges! Memes and gifs!

All of which can be done with HTML, CSS, or UTF-8

Re: LinkedIn uses 2.4 GB RAM across two tabs

#456

Post by tracker1 »

r_lee wrote: post #143
taminka wrote: post #110

Earlier quoted context omitted.

it's unironically just react lmao, virtually every popular react app has an insane number of accidental rerenders triggered by virtually everything, causing it to lag a lot

well that's any framework with vdom, the GC of web frameworks, so I'd imagine it's also a problem with vue etc.. I don't understand though why performance (I.e. using it properly) is not a consideration with these companies that are valued above $100 billion like, do these poor pitiful big tech companies only have the resources to do so when they hit the 2 trillion mark or something?

Well, their lowest tier devs, they have started firing and churn a lot... combined with mass layoffs... and on the higher end, they're more interested in devs that memorized all the leet code challenges over experienced devs/engineers that have a history of delivering solid, well performing applications.

Narcissism rises to the top, excess "enterprise" bloat seeps in at every level combined with too many sub-projects that are disconnected in ways that are hard to "own" as a whole combined with perverse incentives to add features over improving the user experience.

Re: LinkedIn uses 2.4 GB RAM across two tabs

#457

Post by tracker1 »

mike_hearn wrote: post #430
r_lee wrote: post #143

Earlier quoted context omitted.

well that's any framework with vdom, the GC of web frameworks, so I'd imagine it's also a problem with vue etc.. I don't understand though why performance (I.e. using it properly) is not a consideration with these companies that are valued above $100 billion like, do these poor pitiful big tech companies only have the resources to do so when they hit the 2 trillion mark or something?

The React paradigm is just error prone. It's not necessarily about how much you spend. Well paid engineers can still make mistakes that cause unnecesssary re-renders. If you look at older desktop GUI frameworks designed in a performance-oriented era, none of them use the React paradigm, they use property binding. A good example of getting this right is JavaFX which lets you build up functional pipelines that map data…

Property binding and proxies really didn't work well in JS at all until relatively recently, and even then there is actually a much worse history of state management bugs in apps that do utilize those patterns. I've yet to actively use any Angular 1.x app or even most modern Angular apps that don't have bugs as a result of improper state changes.

While more difficult, I think the unidirectional workflows of Redux/Flux patterns when well-managed tend to function much better in that regard, but then you do suffer from potential for redraws... this isn't the core of the DOM overhead though... that usually comes down to a lot of deeply nested node structures combined with complex CSS and more than modest use of oversized images.

Re: LinkedIn uses 2.4 GB RAM across two tabs

#458

Post by conductr »

cosmicgadget wrote: post #378
conductr wrote: post #350

Earlier quoted context omitted.

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

Can you be more specific? Yes I am familiar with LinkedIn.

Their apps do a lot and usually do not run well in my experience. Meaning they can freeze and lock things up on occasion.

Re: LinkedIn uses 2.4 GB RAM across two tabs

#460

Post by arantius »

alyandon wrote: post #176

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

This is a fantastic claim. I've been making web pages since the '90s and using web browsers just as long, and I can't think of a single instance of this. Perhaps it existed and I never knew about it? Can you provide some evidence for where and when this was the case?
Post reply on HN