Timeline
Post
Remote status
Fetching context…
This post replies to something we haven't fetched yet. We'll try to pull in the missing thread context in the background.
@rl_dane @AnachronistJohn @OpenComputeDesign @kabel42
1) supposed to all be the same hardware, I thought, at least for the left side
2) my point is less "safari good" and more "WOW firefox sucks"
Replies
6
@pixx @rl_dane @AnachronistJohn @OpenComputeDesign @kabel42 don't forget Apple Silicon has hardware accelerated an expensive JavaScript function FJCVTZS
Their big.LITTLE arch is smart, their scheduler is smart. It puts most of the work on the lower powered slow cores and only moves them to the fast power hungry cores if they're taking too much cputime
Lots of little tweaks here and there, and they get to compile Safari to take full advantage of the cpu on Macs. Controlling the hardware is a huge benefit
Their big.LITTLE arch is smart, their scheduler is smart. It puts most of the work on the lower powered slow cores and only moves them to the fast power hungry cores if they're taking too much cputime
Lots of little tweaks here and there, and they get to compile Safari to take full advantage of the cpu on Macs. Controlling the hardware is a huge benefit
@feld @OpenComputeDesign @kabel42 @rl_dane @AnachronistJohn
See point 2 :P
firefox is still losing hard there to _everything_ else, not just safari
@pixx @OpenComputeDesign @kabel42 @rl_dane @AnachronistJohn well, I literally sold my MacBook and moved back to FreeBSD as my desktop OS because of bugs I couldn't fix with Safari and MacOS itself. It got to the point that I could try to type in the Safari address bar and I could write an entire website domain and nothing would happen; it was frozen. And then suddenly the last few characters would type. What happened to the rest? Who knows!
Or times when I couldn't click on anything in Safari. It just stopped responding.
Checked cpu usage, nothing was doing anything. Mostly idle. No explanations. Tons of RAM free, my disk wasn't failing...
When you job is mostly flipping back and forth between a browser and a terminal, that was unforgivable.
Idk what the root cause was, but on FreeBSD with Firefox everything is faster. So strange.
Or times when I couldn't click on anything in Safari. It just stopped responding.
Checked cpu usage, nothing was doing anything. Mostly idle. No explanations. Tons of RAM free, my disk wasn't failing...
When you job is mostly flipping back and forth between a browser and a terminal, that was unforgivable.
Idk what the root cause was, but on FreeBSD with Firefox everything is faster. So strange.
@feld @pixx @kabel42 @rl_dane @AnachronistJohn
That's a bit what my recent Linux experience has been like tbh. The BSDs are less bad, but still kinda going that direction tbh.
Although, at least in my case, I'm _usually_ low on RAM, although with plenty of swap left. Though, even with plenty of RAM, Linux is just not as smooth and speedy and reliable as it used to be.
@OpenComputeDesign @pixx @kabel42 @rl_dane @AnachronistJohn at least with Linux you still have the option of slimming with with XFCE or something
I don't like the Linux CPU scheduler or the way it manages memory. Too many bad experiences with it 🫠
I don't like the Linux CPU scheduler or the way it manages memory. Too many bad experiences with it 🫠
@feld @OpenComputeDesign @kabel42 @rl_dane @AnachronistJohn
>hwaccelled js
that's a very fair point though, and I don't think I ever knew that :)