> I reached a point where I could barely hear the podcast I was trying to listen to. That's how loud the fan was.
> focuses mainly on memory usage
I mean I get it, Chrome is not the most efficient browser out there and Safari is more efficient in terms of memory and power usage. I'd probably use Safari as my daily browser if I didn't depend on Chrome's dev tools.
What's the tradeoff though? Usually you sacrifice memory to spare the CPU, and vice versa.
Chrome takes this to an extreme. It has a process per site instance rather than a process per site. You can toggle this by feeding it —-process-per-site as a command line argument.
Safari provides slightly less security in exchange for less resource usage, since some websites allow multiple user accounts to be logged in at the same time and Chrome will protect users data better in those scenarios.
> focuses mainly on memory usage
I mean I get it, Chrome is not the most efficient browser out there and Safari is more efficient in terms of memory and power usage. I'd probably use Safari as my daily browser if I didn't depend on Chrome's dev tools.
What's the tradeoff though? Usually you sacrifice memory to spare the CPU, and vice versa.