Is that true? Maybe it is and I'm out of the loop but I can't remember the last time someone complained about browser speed. The bottleneck seems to be website bloat more than anything else. Would love to see this argument quantified.
How many times a day / week / month do you launch your browser from scratch ?
It is also a moot point with modern processors and modern OSs.
Even more so in Orion's target macOS market where you can leave an app open without any windows open (not minimized, I mean not open at all) , so its ready to go at a click.
Every morning / day across multiple machines. I don't leave them sleeping or hibernated.
Don't think I'd notice a slightly faster browser start; a 50% faster start would be nice though.
But over the last couple months using better window managers like sway or niri, I tend to open new app/browser windows next to the windows they are related to.
It’s pretty nice for mental organization.
Personally, around 5 times per day, every day. When I don't browse, I close the browser
It uses a Free frontend to display Fandom pages, and suggests an alternative non-Fandom wiki when available.
We just don’t know how bad slow browsers can be because all others have caught up.
During that time IE startup time went from a dozen or so seconds to also instantaneous. It was even faster than chrome sometimes. But that was just the startup. The application wasn’t ready to accept any user input or load anything for another 10 or 15 seconds still. Sometimes it would even accept input for a second then block the input fields again.
It’s the same mentality all those insanely slow webapps do when they think some core react feature for a “initial render” or splash screen etc will save them from their horrific engineering practices.
As I recall they cheated by actually starting IE at login time. Window creation is easy to make quick...
A system with less than 64 Megabytes of RAM (most computers of the time) would have to lean heavily on spinning rust virtual memory, making everything slow.
However, since then Chrome has become one of the biggest memory hogs that people commonly run.
Windows Vista, for example, required 512MB but really needed 1GB or more to work.
A year latter, in 2009, Windows 7 was launched, it required 1GB at minimum, but really needed 4GB or more.
Remember that users often don’t correctly figure out which part of the stack is causing something. I’m guessing people generally don’t ID the browser as the performance bottleneck unless they’re familiar with browsers of significantly differing speed, and when not it comes out as asking for faster internet, faster websites, or a faster computer, all of which we hear constantly.
So performance is general is more like it... that includes not hurting my battery life.
Also as a dev Safari is becoming the new IE. I've had a whole suite of Safari-only bugs in the past 2yrs and lots of browser crash reports from users.
Now I think I'll just keep switching until there's one decent browser left which hasn't been AIed.
(Safari with adblocker, of course.)
Orion is faster than Safari on the same Mac. And it isn't rendering speed, but basic UI interface, multi-tabs usage. It is annoying because you see what Webkit is capable of and somehow Apple is not doing such as great job for Mac Safari. The difference is especially true on x86 Mac.
That’s how often I find myself having to do something in a web app that only supports Chrome. Meet the new IE, same as the old IE…
It used to be slow for me, but now on the same hardware it is fast enough that I don't see any difference compared to chrome.
It runs noticeably faster than chrome on my 12 year old laptop. Plus, it isn't riddled with invasive tracking garbage.
I never saw a situation where the actual engine performance mattered in real world scenarios.
These days, all the engines are comparable, except that Google sabotages safari and firefox on its own sites.
I'm on a mac if that matters