Re: How long can Google say the same thing
I think the reason everything was totally isolated was not forced obsolescence.
It was due to their obsessive goal of creating ChromeOS as "just a browser" - do everything on "the cloud" etc.
That fanatical goal slipped through to the design stages too.. A minimal Linux backend, with a big fat browser blob.
Of course, then android compatibility was added... then linux subsystem support, and both of those required the blob to get bigger and more complicated, and they've finally come to their senses and stopped trying to dogmatically create the OS the same way Bill Gates wanted Windows to be created.
A daft decision from the beginning, and I'm sure it was originally forced on the coders from the PR guys.
Another thing with the change to Lacros is currently, the whole OS and bits are installed as one big package, using an A/B root filesytem process. You can get Lacros to install outside this tree, but then the problem is automatic updates.
Before a decoupled Lacros goes mainstream, they'll have to build some kind of automatic updater for it. And how to do that? Either something seperate from Play Store, which is messy from an end-users perspective, or integrate it into Play Store, which is messy from an internal perspective! - Especially as the android subsytem is optional, and play store runs on the android VM.
As an aside, what annoys me most about google is they have brilliant coders, but a complete lack of common sense. Design decisions are often nuts. Functionality is often removed or changed with no option to keep the original default.
One example, they've changed the play store so that you only see reviews for an app from people who have installed on the same type of device. That means that when you visit the play store on a chromeos, there are next to zero reviews of an app visible to you.
Another example - hiding the scroll bar, only making it visible when you move over the scroll area. This means if you don't / can't have a scroll wheel (like with my "TV" connected box), if you want to scroll, you can't move straight to the scroll bar - you have to move to some part on the scroll area, and then up/down to the scroll bar. We recently campaigned for the old method to remain, and they agreed to, but you still have to set that through the obscure flags screen - there is no "clean" option to do so.
And don't get me started on the completely different UI experience between ChromeOS and Android, and how the scrolling is completely different. The android method is brilliant (to scroll, just hold left mouse button and move mouse in X and Y directions. To drag/copy, first hold the left button for a second, and then drag to copy) - the chromeos method only allows drag-copy - like most unix desktops, so its even more annoying that they force us to require the scrollbar, and then make it harder to actually use it!
Ah, I've just gone into a rant again.. Sorry about that!