News for hackers. Stuff that matters.
Re:WebAssembly Studio by brundolf on Thursday December 31, 2020 @11:51AM (#25594326)
The problem is that it's hard to use as a primary language because of a lack of direct Web API access. So basically right now it's not a casual decision to say "I prefer X over JS, so I'll just use that instead because it targets WASM!" Because there's this enormous cost of crossing that API barrier (which means you'll be using some JS regardless, directly or indirectly).

So for now the value-proposition only really makes sense for a fairly narrow subset of projects: mostly ones where client-side pure-compute is a bottleneck. Theoretically API access is being worked on, but I think it's still a ways out.

Re:WebAssembly Studio by postalrat on Thursday December 31, 2020 @03:04PM (#25596540)
Direct access seems improbable and even undesirable. Libraries can be written and shared to expose what you want to the wasm you need to run.
Re:WebAssembly Studio by brundolf on Thursday December 31, 2020 @03:12PM (#25596631)
Lots of people would like the web to become a language-agnostic platform. I don't hate JS the way some do, but even I'd be excited about that prospect. That can never really happen until WASM has direct API access.

That said, I tried just now to find where I read that this was on the long-term roadmap and I'm having trouble finding it. So maybe you're right that it isn't currently planned.