2 ms·
> You start putting everything legacy in a nice little container, and people will freak out when they notice FPS loss or some things being a little odd God for
by JPws_Prntr_Fngr 3y ago
> You start putting everything legacy in a nice little container, and people will freak out when they notice FPS loss or some things being a little odd
God forbid we waste a little processing power on security instead of the ever-expanding slime of bloated frameworks and nonsensical UI.
Seriously, someone competent, please bring an OS to market that can waste my CPU cycles on a robust sandboxing model, a la Android. Take my money. I'm tired of spending it on Apple's constantly degrading UX disaster and security half-assery.
- iggldiggl 3y ago> waste my CPU cycles on a robust sandboxing model, a la Android Unfortunately Android's sandboxing sometimes literally wastes CPU cycles – when Google forced people more seriously to use the new scoped storage API, people stumbled across quite a few performance bugs once you stray past the very simple use cases. And like almost all attempts at file sandboxing (except to a limited extent Apple's implementation for Macs), it's broken interacting with more complex file formats that don't consist of a single atomic file. Using a file explorer to directly open that kind of file (e.g. a local collection of HTML files) in another app has become impossible that way, because the sandboxing system will only grant access to the one single file you've clicked on, and ignore any related file that are implicitly required, too.