Re:WASM Is the New CGI
by tsimionescu on Thursday October 10, 2024 @09:53AM
(#41798843)
It's not the same thing though. All of these languages have specific constructs for integrating with the CLR, the CLR is not just a compilation target like WASM is. C++/CLR even has a fourth kind of variable compared to base C++ (^, managed references of a type, in addition to the base type, * pointers to the type, and & references to the type). IronPython has not had a GIL since its early days. I'm sure the others have significant differences, but I am less aware of them.
[ Parent
| on HN ]
As if WebAssembly doesn't impose similar restrictions, with specific kinds of toolchains, and now the whole components mess.
This WebAssembly marketing is incredible.
Re:WASM Is the New CGI
by tsimionescu on Thursday October 10, 2024 @03:35PM
(#41802632)
Are there any examples of how, say, C++ compiled for WASM is different from native C++, or Python on WASM vs CPython? I haven't really used or cared about WASM, so I'm happy to learn, I don't have some agenda here.