Hmm, fly-solo platform? Check. Totally disregards existing web standards? Check.
Seems quite a ways from "really not."
There are alot of misunderstandings about Google Chrome games supported through (NaCl)
Native
Client libraries. It's nearly the same model as PS Suite using many of the same OPEN SOURCE native language libraries. As long as those native language libraries exist on all platforms, games relying on those libraries are cross platform.
Chrome NaCl games is just WebGL supported with open source native language libraries.
Mono, used by both PS Suite and Google Chrome NaCl, is a Gnome technology and requires Cairo for rendering which requires Glib and Pango; Lua can have Cairo bindings. Both PS Suite and Chrome NaCl run in a
sandbox inside a browser. Mono can API call/use a webkit core (Chrome) and the Android browser core based on webkit had to be rewritten to comply with webkit API standards to be used with PS Suite and it looks like in the near future we will hear that Android's browser is going to support Google Chrome NaCl games.
A difference between PS Suite and Chrome
Native
Client looks to be in the choices for the game engines and AV support. Sony went with gstreamer and Chrome NaCl is using a different sound only library. PS Suite appears to have longer legs (more powerful) while Googles choices allow for a larger more open, more inclusive platform. (This only from looking at the Sony Google TV and other CE disclosures on-line.)
A Linux or POSIX platform using a GTK webkit browser is already more than half way to supporting PS Suite and slightly less for Chrome's NaCl model as the support libraries chosen for webkit with WebGL support are the same as needed by PS suite and to a lesser extent Chrome's NaCl. The PS3 is getting a GTKwebkit WebGL browser.
What's not clear to me is if this is to be part of a WebGL standard in the future. Middleware
PS3 Home
Lua with Cairo bindings (could convert to Mono for scripting)
CairoGL
Gstreamer
Pango
Glib
webkit core? no proof of this but probably coming
Game Engine (Unknown)
Physics Engine (unknown)
Lua with Cairo bindings as of Home Client 1.4
As of Client 1.4 supports the Gstreamer DASH player and possibly Webkit core
Client 1.5 introduces a new Game engine (unknown possibly Phyre) and Physics engine (unknown rumored to be Havoc) The unknowns beg the question, what if Sony is using the same choices made by Google Chrome NaCL??? The PS3 has more free memory than is being used by Home and Hard Disk cache/virtual memory is being used in a manner like a handheld Vita or Android platform not like one with a hard disk. This leads to speculation that Sony has plans for "Home" on other platforms.
GTKwebkit coming to the PS3
webkit core (May require webkit2)
GTK
CairoGL
Pango
Gstreamer 1.0 with Cairo bindings (Audio and Video)
Glib
PS Suite on Android platforms in a Android NDK enabled MonoJIT sandbox
Webkit core (webkit2)
Mono (C & C++ compiled to C# then Mono bytecode)
GTK
CairoGL
Pango
Gstreamer 1.0 with Cairo bindings (Audio and Video)
Glib
Game engine (unknown) OpenGL
Physics engine (unknown)
Google Chrome NaCl Game = NaCl in a Chrome Browser Sandbox = WebGL + Native Client Libraries
webkit core (webkit2)
Mono
CairoGL
Pango
Glib
Fmod Wwise (Audio)
Game engine (Unity and Moai) OpenGL
Physics Engine (Bullet)
Lua with Cairo Bindings
Native code compilers from many langagues including C, C++, and C# (may be part of the Mono package C & C++ compiled to C# then Mono bytecode)