[esperkin39]

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.

[ajross]

> Then it is correct? Many of the Fugu APIs don't work. I didn't say none

You claimed that support was significantly worse than on Mac or Windows, and the chart certainly doesn't bear that out.

And your examples seem... pretty cherry picked? I mean, there's junk that fails everywhere. If color pickers are core to your job, then... OK, I guess. It's a hole. It doesn't seem to remotely justify the kind of bile and hatred you're deploying here.

[esperkin39]

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.

[ajross]

> 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.

Which is kinda what I thought. This isn't about your upthread point about Fugu. You're doing a platform advocacy thing, which I'm not interested in. I jumped in to point out that it's simply not true that Fugu is poorly supported in ChromeOS, because it's not. I'm not trying to have a fight about platforms.