|
|
|
|
|
|
by burgerboy
2748 days ago
|
|
|
What a nonsense statement. Would you rather this project just not exist at all rather then use a technology specific to chrome? It's like saying because an app using the Mac touch bar is Mac only is a terrible thing. It's not. It's how platforms work. |
|
|
So, because I think Google shouldn't use a technology that they themselves marked as deprecated, leaving it only supported in their own browser using their own technology that only they implemented, it shouldn't exist in any way shape or form — despite the fact that wasm is already supported in Chrome and other web browsers?
Obviously, they should have just waited until they'd finished porting to wasm. The world would have survived without the NaCl version of a tool they never had before; bloods wouldn't run down the streets if we'd have had to wait a little bit longer for the only version of the tool that should have released.
> It's like saying because an app using the Mac touch bar is Mac only is a terrible thing
It's really not. The touch bar doesn't purport to be a standards-compliant technology available for every platform to access in an equitable way; apart from the fact it's only on Macs, nothing about it was ever advertised as being explicitly designed for cross-platform use.
The analogy to Chrome, a browser that is advertised as standards-compliant and even advancing standards, to the extent that it already includes wasm support, utterly falls apart.
> It's how platforms work
Chrome is not a platform, and I find myself shocked when anybody thinks so. It's as though the lessons of the past (IE, ActiveX, plugin lock-in) remain unlearnt; a new generation of people who don't know how good they've had it for so long.
Chrome is __not__ a platform; it is merely the window through which we consume the real platform: the open web.
When Google tries to push Chrome as a platform, we need to all push back. We've had one browser as a platform, and it was not good, it was unhealthy for developers as well as advancements in web technologies, and I and anybody who still has to support IE5 and IE6 do not want to see that again.