3 ms·

The Chrome versions of the first few years were so nice to use. It was the _lightest_ major browser for a time. It's insane how it has drifted since then.

crazygringo 3y ago
Has it drifted? I don't see it. I think all the other browsers just had to become light and fast too. Even Microsoft was forced to say goodbye to IE, and instead based Edge on Chromium. And tech people were eventually able to switch back to Firefox because it got much faster too. Google wanted a world where all browsers were light and fast in order to efficiently run complex webapps -- and they achieved that. Kudos.
- dazzlefruit 3y ago
  Chrome is often criticized for overusing RAM. Personally I stopped using it a couple years ago, but when I stopped, it was very far from light; I remember it freezing for a few seconds for lack of RAM in a way other browsers (Firefox with multiprocessing, Edge before it got rebuilt over Chromium) didn't. The original Chrome just felt like a barebones window to the Internet. Though I agree that Firefox et al. became much less sluggish over time. (Is that only their performance improvements or did hardware get better faster than they grew?) Also maybe "light" and "fast" shouldn't be lumped together. Chrome can definitely be fast when it has enough resources. That and sandboxing seem to make it much _heavier_ in RAM.
  - eric-hu 3y ago
    As a web developer I also have to tell you that my industry has gotten more cavalier about using resources. Unless your benchmark is browsing sites that you know have not changed in 15 years, the heaviness you feel could be from development teams using shiny new frameworks.
  - dmazzoni 3y ago
    Chrome isn't using all that RAM. The web pages you visit are.
dmazzoni 3y ago
Did it really? Because browsers got good, the web got orders of magnitude more complex. If you try loading a modern web page in an old version of Chrome, you'll see just how much faster Chrome has gotten. Or alternatively, try viewing an old webpage in new Chrome. It's still super light and zippy.
- callalex 3y ago
  Yes, feature creep has happened in a really big way because there is an obvious profit incentive to Google if every last bit of computing happens in-browser. Glossing over the thorny topics like “my browser shouldn’t care what hardware I run it on”, the Web* set of standards hasn’t stopped ballooning since the release of chrome. WebRTC made sense. But WebUSB? WebGPU? WebAssembly? etc. etc. Each can have interesting use cases individually, but in aggregate they have become a whole second operating system filled with compromise and bloat.
Andrew_nenakhov 3y ago
It also looked much nicer. These thick curved tab decorations, unnecessary ovals everywhere, yuck.

crazygringo 3y ago

Has it drifted? I don't see it. I think all the other browsers just had to become light and fast too. Even Microsoft was forced to say goodbye to IE, and instead based Edge on Chromium. And tech people were eventually able to switch back to Firefox because it got much faster too. Google wanted a world where all browsers were light and fast in order to efficiently run complex webapps -- and they achieved that. Kudos.

dazzlefruit 3y ago
Chrome is often criticized for overusing RAM. Personally I stopped using it a couple years ago, but when I stopped, it was very far from light; I remember it freezing for a few seconds for lack of RAM in a way other browsers (Firefox with multiprocessing, Edge before it got rebuilt over Chromium) didn't. The original Chrome just felt like a barebones window to the Internet. Though I agree that Firefox et al. became much less sluggish over time. (Is that only their performance improvements or did hardware get better faster than they grew?) Also maybe "light" and "fast" shouldn't be lumped together. Chrome can definitely be fast when it has enough resources. That and sandboxing seem to make it much _heavier_ in RAM.
- eric-hu 3y ago
  As a web developer I also have to tell you that my industry has gotten more cavalier about using resources. Unless your benchmark is browsing sites that you know have not changed in 15 years, the heaviness you feel could be from development teams using shiny new frameworks.
- dmazzoni 3y ago
  Chrome isn't using all that RAM. The web pages you visit are.

dmazzoni 3y ago

Did it really? Because browsers got good, the web got orders of magnitude more complex. If you try loading a modern web page in an old version of Chrome, you'll see just how much faster Chrome has gotten. Or alternatively, try viewing an old webpage in new Chrome. It's still super light and zippy.

callalex 3y ago
Yes, feature creep has happened in a really big way because there is an obvious profit incentive to Google if every last bit of computing happens in-browser. Glossing over the thorny topics like “my browser shouldn’t care what hardware I run it on”, the Web* set of standards hasn’t stopped ballooning since the release of chrome. WebRTC made sense. But WebUSB? WebGPU? WebAssembly? etc. etc. Each can have interesting use cases individually, but in aggregate they have become a whole second operating system filled with compromise and bloat.

Andrew_nenakhov 3y ago

It also looked much nicer. These thick curved tab decorations, unnecessary ovals everywhere, yuck.