WebAssembly Studio
webassembly.studio
WebAssembly Studio
1–10 of 231 posts
Re: WebAssembly Studio
#2Jokes about the [Birth and Death of JavaScript](https://www.destroyallsoftware.com/talks/the-birth-and-death...) aside, I love the concept of WASM and that we're making the web a more robust compile target.
One of the big limitations in my mind is that I still don't know of that many people using it in production at scale. Is there a list, or well known set of examples (other than Figma), who are using WASM in prod?
Re: WebAssembly Studio
#3Jokes about the [Birth and Death of JavaScript]( https://www.destroyallsoftware.com/talks/the-birth-and-death... ) aside, I love the concept of WASM and that we're making the web a more robust compile target. One of the big limitations in my mind is that I still don't know of that many people using it in production at scale. Is there a list, or well known set of examples (other than Figma), who are using WASM in prod…
Shopify is using WASM in production [0]
Re: WebAssembly Studio
#4Seeing gulp being used in the examples for the build step is strange... I wonder why it was chosen. Nothing wrong with it per se but gives me flashbacks to the horrors of my past exposure to it as an inexperienced webdev.
Re: WebAssembly Studio
#5Jokes about the [Birth and Death of JavaScript]( https://www.destroyallsoftware.com/talks/the-birth-and-death... ) aside, I love the concept of WASM and that we're making the web a more robust compile target. One of the big limitations in my mind is that I still don't know of that many people using it in production at scale. Is there a list, or well known set of examples (other than Figma), who are using WASM in prod…
Autodesk.
https://www.infoq.com/presentations/autocad-webassembly/
https://blogs.autodesk.com/autocad/autocad-web-app-google-io...
https://forge.autodesk.com/blog/load-encrypted-model-data-we...
BabylonJS plugins
https://babylonjs.medium.com/marker-tracking-in-babylon-js-c...
Blazor
https://dotnet.microsoft.com/apps/aspnet/web-apps/blazor
Uno
Re: WebAssembly Studio
#6I find it a nice experience, but as far as I am aware it is pretty much dead, the website just happens to keep running.
Re: WebAssembly Studio
#7I find it a nice experience, but as far as I am aware it is pretty much dead, the website just happens to keep running.
Yep, it's not actively developed : https://github.com/wasdk/WebAssemblyStudio/commits/master
Re: WebAssembly Studio
#8Seeing gulp being used in the examples for the build step is strange... I wonder why it was chosen. Nothing wrong with it per se but gives me flashbacks to the horrors of my past exposure to it as an inexperienced webdev.
I only did one Gulp project and read it was a drastic improvement over Grunt, which I didn't use.
But most of my projects were done with Webpack and NPM scripts.
Re: WebAssembly Studio
#9Jokes about the [Birth and Death of JavaScript]( https://www.destroyallsoftware.com/talks/the-birth-and-death... ) aside, I love the concept of WASM and that we're making the web a more robust compile target. One of the big limitations in my mind is that I still don't know of that many people using it in production at scale. Is there a list, or well known set of examples (other than Figma), who are using WASM in prod…
Figma is written in C++, compiled to WebAssembly. Probably the most advanced web-based design tool in the world.
I think they have like 4-5M users, and a $2B valuation.
Re: WebAssembly Studio
#10The "Create New Project" dialog has serious accessibility problems when used with a screen reader. The buttons are clickable divs, not actual HTML buttons or even marked up with proper ARIA. I haven't yet ventured any further into the app.
Given that the app is a WebAssembly development environment, my first guess was that it was built in WebAssembly itself, with a custom UI framework. But in fact, it's plain React, using its own home-grown components for basic things like buttons.
It breaks my heart that when this project was started in 2017, some 20 years after web accessibility advocacy had started in earnest, the developer was still uninformed enough about accessibility that they would create a custom button component with no ARIA support. I suppose we could also blame the web platform for making it hard enough to customize the look of a standard button that the developer would reach for the div tag. What do we do about this?