I could go on and on
To that we're in no doubt. Too bad you didn't find the time to critically appraise what you've read on some woo website before mindlessly parroting it..
Of course if he weren't such a narcissist he wouldn't have resorted to such ludicrous measures in the first place.
Aside from that, most phone operating systems have a partition for the system and a user partition. If an iPhone follows this kind of layout then I don't see how removing apps will help unless the device can be re-partitioned during an upgrade to reclaim the space. It's actually more likely to waste space because if Apple update these apps then the phone will hold the stock version in the system partition and a more recent one in the user partition. It's now wasted 2x the space. The same crap happens on Android phones where the firmware will often have burnt-in copies of Facebook, Gmail, Twitter etc which are immediately superseded.
It seems more likely that they'll toss in 4K support for streaming services and leave it at that.
Microsoft originally intended to embed a unique serial # into each disc so that it became bound to the first account that played the game. A bit like a product code. Turns out people really hated that idea. It was partly this and the Kinect debacle that gave the PS4 an early lead.
Or watch as this happens over and over again.
Chrome uses plugin called PDFium. This is a C++ based plugin that takes care of rendering the PDF and its output. It's faster and produces better prints but it's also an attack surface in its own right. The exploit in this case was in a 3rd party dependency openjpeg which could be exploited.
Personally I think the JS approach is the way to go, although it would be nice if it would refine how it renders the canvas DPI / backing store so the quality was better. And I believe browsers are better off with a PDF viewer. External viewers are a source of far more exploits than one that is built-in, especially since Chrome / Firefox can force updates for critical issues. But it can still be turned off if someone is paranoid or prefers to use an external viewer.
Many Chromebook applications are front ends to cloud based services. If Google decides to end of life one of those services then you're screwed. And this has happened before such as when YouTube end-of-lifed an older client API. So yeah your chromebook might work for a while and then gradually bitrot and break as one service after another is withdrawn.
Aside from the cloud services, chances are the browser will be start breaking over time too. Sites that expect chrome won't be happy about some 2 or 3 year old version and will start throwing up errors to upgrade and so on. Except of course you can't upgrade.
"An entire fraternity of strapping Wall-Street-bound youth. Hell - this is going to be a blood bath!" -- Post Bros. Comics