Boombox On
Member
(By "Portability," I mean the ability of software to be transferred from any one system to another easily)
To me, Webassembly is one of the more intriguing recent software technologies. It's super early, but it's a low-level language designed for high end webapps to compile to. This means that high end C++ programs can run inside of a browser, but what makes it different than similar efforts from before is that Webassembly is a agreed upon, built-in web browser standard that all major browsers (Chrome, Firefox, Edge, and Safari) will support. Nothing is perfect though, and there is a performance hit when comparing a "webassembly app" to a native program running directly on the OS.
And it had me thinking about how gamers, specifically PC gamers, would look at something like this. So let's paint a hypothetical situation; Let's say there was a parallel universe where your entire PC gaming library as it stands right now runs in a web browser, and all games by default run across Windows, Mac, Linux, (if the hardware can manage it) iOS, Android, and any future Operating System that may not exist yet. You have the freedom to change browsers, operating systems, or ecosystems as much as you want and the games will generally work the same. The downside is there is a 50% hit on performance. CPU, GPU, RAM, everything. You would need to pay for double the hardware power to get the same performance on the same games as you do now.
Would you want it?
(Side note, Webassembly shouldn't be this taxing on performance. I just pushed it out to an extreme to make the discussion a bit more interesting)
To me, Webassembly is one of the more intriguing recent software technologies. It's super early, but it's a low-level language designed for high end webapps to compile to. This means that high end C++ programs can run inside of a browser, but what makes it different than similar efforts from before is that Webassembly is a agreed upon, built-in web browser standard that all major browsers (Chrome, Firefox, Edge, and Safari) will support. Nothing is perfect though, and there is a performance hit when comparing a "webassembly app" to a native program running directly on the OS.
And it had me thinking about how gamers, specifically PC gamers, would look at something like this. So let's paint a hypothetical situation; Let's say there was a parallel universe where your entire PC gaming library as it stands right now runs in a web browser, and all games by default run across Windows, Mac, Linux, (if the hardware can manage it) iOS, Android, and any future Operating System that may not exist yet. You have the freedom to change browsers, operating systems, or ecosystems as much as you want and the games will generally work the same. The downside is there is a 50% hit on performance. CPU, GPU, RAM, everything. You would need to pay for double the hardware power to get the same performance on the same games as you do now.
Would you want it?
(Side note, Webassembly shouldn't be this taxing on performance. I just pushed it out to an extreme to make the discussion a bit more interesting)