6 ms·

We now have simple chat apps capable of doing almost anything LinkedIn does while using under 100 MB of RAM.

by nshelia 6mo ago

denysvitali 6mo ago
A probe collecting data in space takes <70 kB of memory. I fail to see how this statement should make me feel happy
- mattmanser 6mo ago
  As someone was pointing out in a thread the other day about memory usage, a lot is fonts and images. EDIT: Just mind boggling to get d/v'ed for pointing out voyager doesn't have to render fonts or images...
  - littlestymaar 6mo ago
    Aka poor resources management. If you have significantly more images loaded in RAM than what fits on your screen, something wrong is going on. (Not counting the filesystem cache here, because it works in a best effort way).
    - deleted 6mo ago
      [deleted]
    - ben-schaaf 6mo ago
      The alternative is that for every glyph you render the entire glyph to the screen using the Bezier curves from the font, and you end up with dogshit performance - like the new windows terminal (not sure if they've fixed it yet). Caching glyphs is good resource management and with modern screen resolutions, color displays and subpixel-antialiasing you just simply need more than 70KB of RAM.
      - littlestymaar 6mo ago
        > The alternative is that for every glyph you render the entire glyph to the screen using the Bezier curves from the font No, because you have no reason to have much more glyphs in your font cache than what fits your screen either (for people using a language with an alphabet based on the latin one at least, which is the majority of people on this website). > you just simply need more than 70KB of RAM. I didn't set the bar to 70kB. You also need more than 70kB of RAM yo store a full screen worth of image (which was the bar I set above). But that doesn't mean you need 1GB either.
        ben-schaaf 6mo ago
        > I didn't set the bar to 70kB The GP to your original did set the bar at 70kB, mattmanser then explained that images and fonts easily exceed that, and then you called that poor resource management. Sounds like we're on the same page here, but you seemed to have missed the context of the comment you initially replied to.
        littlestymaar 6mo ago
        > The GP to your original did set the bar at 70kB It didn't, here's the comment in question: > A probe collecting data in space takes <70 kB of memory. I fail to see how this statement should make me feel happy It makes no mention that an app should be under 70kB. It just note that 100MB is still *enormous* compared to 70kB. And I maintain that the difference cannot be explained by images and font cache alone.
        ben-schaaf 6mo ago
        > And I maintain that the difference cannot be explained by images and font cache alone. It can't be explained by images and fonts alone, I agree, but images and fonts alone are still enormous compared to 70kB. On my screen an "e" on this site is 10*11 pixels. Subpixel positioning means we need at least 6 copies of each letter, subpixel antialiasing means we need three channel alpha (3 bytes per pixel), we have variations of bold, italic and bold-italic, 95 printable letters in ascii, that's a low-ball of 750kB for one size of one font. This comment page alone has 4 different sizes, I'd expect a chat app to have a few more.
  - cosmicgadget 6mo ago
    How much? You typically don't want more than a few different fonts on a given document. And neither fonts nor web images should be bigger than hundreds of kilobytes. How do we get to gigs?
    - conductr 6mo ago
      > 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.
      - cosmicgadget 6mo ago
        Can you be more specific? Yes I am familiar with LinkedIn.
        conductr 6mo ago
        Their apps do a lot and usually do not run well in my experience. Meaning they can freeze and lock things up on occasion.
      - heyethan 6mo ago
        [flagged]
    - stackghost 6mo ago
      >How do we get to gigs? Microsoft, who has owned LinkedIn since 2016, has recently been making headlines because recently they fired a lot of their engineers and QA staff and are now essentially vibecoding huge chunks of their enterprise. What's more, Microsoft never paid the really big bucks like the FAANG companies, and so it's more or less an open secret that at the height of the tech hiring frenzy Microsoft had to fight for B-tier engineers that weren't good enough to work at e.g. Apple. So, it's been 10 years, which is long enough for that trademark Microsoft mediocrity to seep into LinkedIn. And they're probably vibe coding everything. That's how you get to gigs.
      - 6mo ago
  - troupo 6mo ago
    Well, and then you have Claude Code which at one point needed 68GB of RAM to run https://x.com/jarredsumner/status/2026497606575398987 https://x.com/jarredsumner/status/2026497606575398987 :)
- ozim 6mo ago
  Space is mostly empty there is not much interesting stuff to collect and who’s going to buy that data LinkedIn on the other hand has user behavior, computer details etc. that’s a lot of interesting data.
  - bryanrasmussen 6mo ago
    >Space is mostly empty Yes, but Space is big. Really big. You just won't believe how vastly, hugely, mind-bogglingly big it is. I mean, you may think it's a long way down the road to the chemist's, but that's just peanuts to space.
    - ozim 6mo ago
      Exactly and people on LinkedIn think they are smarter than everyone and definitely smarter than dolphins, because what dolphins do? They muck in the water all day having good time whereas humans built important profiles on LinkedIn having good time berating each other.
thephyber 6mo ago
I’m guessing you mean “does” in the sense of a user-facing feature. I’ve heard that LinkedIn searches for several hundred known browser plugins to identify potential abusive users. If the “simple chat apps” aren’t doing that, then it’s apples-to-oranges.
weare138 6mo ago
I remember when your computer had 128MB of ram and could still run an entire desktop OS, web browser and chat app at the same time.

We now have simple chat apps capable of doing almost anything LinkedIn does while using under 100 MB of RAM.

by nshelia 6mo ago

We now have simple chat apps capable of doing almost anything LinkedIn does while using under 100 MB of RAM.

denysvitali 6mo ago

A probe collecting data in space takes <70 kB of memory. I fail to see how this statement should make me feel happy

mattmanser 6mo ago
As someone was pointing out in a thread the other day about memory usage, a lot is fonts and images. EDIT: Just mind boggling to get d/v'ed for pointing out voyager doesn't have to render fonts or images...
- littlestymaar 6mo ago
  Aka poor resources management. If you have significantly more images loaded in RAM than what fits on your screen, something wrong is going on. (Not counting the filesystem cache here, because it works in a best effort way).
  - deleted 6mo ago
    [deleted]
  - ben-schaaf 6mo ago
    The alternative is that for every glyph you render the entire glyph to the screen using the Bezier curves from the font, and you end up with dogshit performance - like the new windows terminal (not sure if they've fixed it yet). Caching glyphs is good resource management and with modern screen resolutions, color displays and subpixel-antialiasing you just simply need more than 70KB of RAM.
    - littlestymaar 6mo ago
      > The alternative is that for every glyph you render the entire glyph to the screen using the Bezier curves from the font No, because you have no reason to have much more glyphs in your font cache than what fits your screen either (for people using a language with an alphabet based on the latin one at least, which is the majority of people on this website). > you just simply need more than 70KB of RAM. I didn't set the bar to 70kB. You also need more than 70kB of RAM yo store a full screen worth of image (which was the bar I set above). But that doesn't mean you need 1GB either.
      - ben-schaaf 6mo ago
        > I didn't set the bar to 70kB The GP to your original did set the bar at 70kB, mattmanser then explained that images and fonts easily exceed that, and then you called that poor resource management. Sounds like we're on the same page here, but you seemed to have missed the context of the comment you initially replied to.
        littlestymaar 6mo ago
        > The GP to your original did set the bar at 70kB It didn't, here's the comment in question: > A probe collecting data in space takes <70 kB of memory. I fail to see how this statement should make me feel happy It makes no mention that an app should be under 70kB. It just note that 100MB is still *enormous* compared to 70kB. And I maintain that the difference cannot be explained by images and font cache alone.
        ben-schaaf 6mo ago
        > And I maintain that the difference cannot be explained by images and font cache alone. It can't be explained by images and fonts alone, I agree, but images and fonts alone are still enormous compared to 70kB. On my screen an "e" on this site is 10*11 pixels. Subpixel positioning means we need at least 6 copies of each letter, subpixel antialiasing means we need three channel alpha (3 bytes per pixel), we have variations of bold, italic and bold-italic, 95 printable letters in ascii, that's a low-ball of 750kB for one size of one font. This comment page alone has 4 different sizes, I'd expect a chat app to have a few more.
- cosmicgadget 6mo ago
  How much? You typically don't want more than a few different fonts on a given document. And neither fonts nor web images should be bigger than hundreds of kilobytes. How do we get to gigs?
  - conductr 6mo ago
    > 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.
    - cosmicgadget 6mo ago
      Can you be more specific? Yes I am familiar with LinkedIn.
      - conductr 6mo ago
        Their apps do a lot and usually do not run well in my experience. Meaning they can freeze and lock things up on occasion.
    - heyethan 6mo ago
      [flagged]
  - stackghost 6mo ago
    >How do we get to gigs? Microsoft, who has owned LinkedIn since 2016, has recently been making headlines because recently they fired a lot of their engineers and QA staff and are now essentially vibecoding huge chunks of their enterprise. What's more, Microsoft never paid the really big bucks like the FAANG companies, and so it's more or less an open secret that at the height of the tech hiring frenzy Microsoft had to fight for B-tier engineers that weren't good enough to work at e.g. Apple. So, it's been 10 years, which is long enough for that trademark Microsoft mediocrity to seep into LinkedIn. And they're probably vibe coding everything. That's how you get to gigs.
    - 6mo ago
- troupo 6mo ago
  Well, and then you have Claude Code which at one point needed 68GB of RAM to run https://x.com/jarredsumner/status/2026497606575398987 https://x.com/jarredsumner/status/2026497606575398987 :)
ozim 6mo ago
Space is mostly empty there is not much interesting stuff to collect and who’s going to buy that data LinkedIn on the other hand has user behavior, computer details etc. that’s a lot of interesting data.
- bryanrasmussen 6mo ago
  >Space is mostly empty Yes, but Space is big. Really big. You just won't believe how vastly, hugely, mind-bogglingly big it is. I mean, you may think it's a long way down the road to the chemist's, but that's just peanuts to space.
  - ozim 6mo ago
    Exactly and people on LinkedIn think they are smarter than everyone and definitely smarter than dolphins, because what dolphins do? They muck in the water all day having good time whereas humans built important profiles on LinkedIn having good time berating each other.

thephyber 6mo ago

I’m guessing you mean “does” in the sense of a user-facing feature. I’ve heard that LinkedIn searches for several hundred known browser plugins to identify potential abusive users. If the “simple chat apps” aren’t doing that, then it’s apples-to-oranges.

weare138 6mo ago

I remember when your computer had 128MB of ram and could still run an entire desktop OS, web browser and chat app at the same time.