I haven't made anything particularly useful, but conceptually I really love WASM and think it has a very bright potential. I don't think the tooling is quite there yet, but it's still a new tech and for being as new as it is, browser adoption is fantastic.
As someone very interested in programming language design, the recent #discuss topic Hating on languages you don't use piqued my interest. I have my opinions about some of the languages out there but I was glad to see in the comments one of my favorite observations about the various programming languages out there.
Turing complete languages are essentially just morphisms of finite state automata, so why argue about the packaging?
When performance is the same, the only thing worth arguing about in language design is the grammar. And while I personally love JavaScript many out there would love to see JS's monopoly on the Web come to an end. And they are totally valid in having that opinion. WASM to me, is the answer to that. A common compilation target that any new or old language could come in and target and experience the same performance that browsers have been working on for so long.
To wrap back, I really like a lot about TypeScript and would love a way for it to be interpreted in a more "native-like" way on the Web (instead of just back compilation)
I'm a fan of Open Source and have a growing interest in serverless and edge computing. I'm not a big fan of spiders, but they're doing good work eating bugs. I also stream on Twitch.
I haven't made anything particularly useful, but conceptually I really love WASM and think it has a very bright potential. I don't think the tooling is quite there yet, but it's still a new tech and for being as new as it is, browser adoption is fantastic.
As someone very interested in programming language design, the recent #discuss topic Hating on languages you don't use piqued my interest. I have my opinions about some of the languages out there but I was glad to see in the comments one of my favorite observations about the various programming languages out there.
When performance is the same, the only thing worth arguing about in language design is the grammar. And while I personally love JavaScript many out there would love to see JS's monopoly on the Web come to an end. And they are totally valid in having that opinion. WASM to me, is the answer to that. A common compilation target that any new or old language could come in and target and experience the same performance that browsers have been working on for so long.
To wrap back, I really like a lot about TypeScript and would love a way for it to be interpreted in a more "native-like" way on the Web (instead of just back compilation)
Sounds like you should write a post about WASM ;)