Because despite the hyperbolic praise of the hackers here, Apple devices are worthless for some professional workloads.
Before you ask, I'm one user who has a Razer Blade 16 (4090) and Galaxy Book 4 Ultra that I use for CAD and BIM work. I'll pass on having a dedicated video editor.
Apple sells good hardware that's buoyed by a loud marketing department that covers its often pathetic software.
Mac users touting a bunch of third-party apps as solutions to obvious os problems (bartender, magnet, amphetamine, etc.) is tacit admission of that fact.
I gave another example as well. I'm also not spewing any "hate" or "bile" for an inanimate operating system.
To make this easier to understand, please give me an example of what's missing from Mac or Windows and I'll share the way it can easily be accomplished in a native environment. After that, we can try to do the same for ChromeOS and you'll see where the holes appear.
Fugu is about slowly moving Mac and Windows functions to the web, but ChromeOS exists RIGHT NOW. Thus, if it were for that platform, there would be urgency and full support across the board. Because they don't care about filling all those holes, they choose not to support every API.
That was my point. Windows and Mac don't need Fugu to function. ChromeOS does. Still, Windows and Mac needs are prioritized over ChromeOS.
I also noticed you deftly ahem cherry-picked around the lack of server support on a web-first operating system, but that's neither here nor there.
Then it is correct? Many of the Fugu APIs don't work.
I didn't say none.
You can always tell someone hasn't developed consumer apps for ChromeOS when they white knight for it.
If you want to know a specific API that DOESN'T work, but performs splendidly on Windows, then the Eyedropper is a perfect example.
There's an old bug report for it that even has Google Chrome team support, and still no dice.
But yeah, keep rushing to defend the platform that doesn't even get proper support from its creators.
Another example is given in the link you posted. Direct Sockets API is deprecated, but its replacement isn't available yet.
So, if you were a web-dev using "vanilla" ChromeOS to test a site, you better install a full Debian VM on your 4 gb machine, because there's no other way to spin up a server.
No, I think it was correct to say Fugu is NOT for ChromeOS.
Unfortunately, Fugu is totally seperate from ChromeOS, since many of Fugus capabilities don't work on the platform. Still, on Windows and Mac, Fugu is definitely more impressive than anything ChromeOS is doing.
Versatile is the opposite of what ChromeOS has become. I would argue that there was a time (beginning of pandemic) where it looked like Google might strike the perfect balance between web-reliant (PWAs and safer extensions) and legacy-OS supported (Android, Linux, and even some slight Windows compatibility).
Now, it just seems like a bad version of the legacy operating systems. Android, but in a VM, Linux, but in a VM, and Windows delivered via the cloud!
All of this is worse than just running any of those systems alone.
For better or for worse, that's what Google is aiming at with ChromeOS. Especially now that the overarching "OS" is really just a Linux shell for multiple VMs.
Before you ask, I'm one user who has a Razer Blade 16 (4090) and Galaxy Book 4 Ultra that I use for CAD and BIM work. I'll pass on having a dedicated video editor.