News for hackers. Stuff that matters.

A comment on Splix.io. Parent comment

Re:Splix.io by danellis on Monday October 24, 2016 @04:14AM (#12777308)
No kidding -- after a couple of minutes of play, it brought my 32GB Mac to a near halt.
[ Parent | on HN ]
Re:Splix.io by subinsebastien on Monday October 24, 2016 @06:48AM (#12777802)
In one minute, I had to force Quit chrome on my mac.
[ Parent | on HN ]
Re:Splix.io by iconjack on Monday October 24, 2016 @08:44AM (#12778252)
Doesn't that mean your OS is rather broken as well?
[ Parent | on HN ]
Re:Splix.io by BoorishBears on Monday October 24, 2016 @09:03AM (#12778366)
Broken for respecting it's owners wish to run a program with most of the resources available to it?
[ Parent | on HN ]
Re:Splix.io by pritambaral on Tuesday October 25, 2016 @12:55AM (#12785393)
Tangentially related — and I'm not dissing on OS X here — but I really like the Linux kernel's Magic SysRq keys. It's a simple concept: no matter what software does, the hardware will always pass through the kernel first; so set up special keybindings to command the kernel to do special things.

Alt-SysRq-f pulls out the OOM killer, which targets the worst memory abusing process and just mercilessly kills it. It's super handy on a desktop OS that's frequently pushed to its limits. Chrome eating too much RAM? Pull out Alt-SysRq-f and kill the fattest Chrome process!

[ Parent | on HN ]
Re:Splix.io by danellis on Thursday October 27, 2016 @09:10PM (#12812064)
It is never my wish to devote so many resources to a program that the desktop becomes unresponsive.
[ Parent | on HN ]
Re:Splix.io by danellis on Thursday October 27, 2016 @09:09PM (#12812053)
Yep. There should at least be some kind of high-priority kill switch for that sort of thing.
[ Parent | on HN ]