3 ms·

"[...] this allows Haskell to be used as a scripting language for Microsoft's Internet Explorer web browser". Interesting. Never heard of that. https://www.mic

by dloss 6y ago

"[...] this allows Haskell to be used as a scripting language for Microsoft's Internet Explorer web browser". Interesting. Never heard of that. https://www.microsoft.com/en-us/research/publication/scripting-com-components-haskell/ https://www.microsoft.com/en-us/research/publication/scripti... EDIT: Add link

LockAndLol 6y ago
If WASM had access to the DOM, I imagine we'd start seeing a replacement of JS and a democratization of web languages. I however dread the day I get to read a full-stack C/C++ webpage.
- gridlockd 6y ago
  You can give WASM access to the DOM. What you describe is already possible, but most language runtimes are too big to be served for a website.
  - rowanG077 6y ago
    Are there efforts to cache runtimes? I imagine most programs would be rather small if you don't have to ship the runtime.
    - gridlockd 6y ago
      There isn't really a good workflow regarding dynamic linking and libraries in WASM right now, but things are moving. Even then, what are the odds that your new user already has the particular version of your runtime cached already? If you really have a non-trivial application, then downloading the runtime isn't that big a deal I guess. If you just have a website, it wouldn't be warranted. Having said that, if you're careful, you can use Rust[1] or C/C++[2] with minimal overhead. I doubt that's going to become popular though. [1] https://www.hellorust.com/demos/add/index.html https://www.hellorust.com/demos/add/index.html [2] https://floooh.github.io/sokol-html5/index.html https://floooh.github.io/sokol-html5/index.html
      - rowanG077 6y ago
        Well the chances are low if it's the first time he is visiting my site. But since this will be used for web apps the chances are very high that a user will revisit.
        gridlockd 6y ago
        That case is already covered by browser caching.
- dep_b 6y ago
  You can get a full-stack .net webpage with Blazor already
  - tasogare 6y ago
    I’ve been playing with it in the last two days, and while it’s a bit annoying to have to deal with CSS for UI instead of XAML and the recompilation cycle, the framework is impressive. A lot of things can be done without touching JavaScript directly, and when in need the interop works well.

by dloss 6y ago

LockAndLol 6y ago

If WASM had access to the DOM, I imagine we'd start seeing a replacement of JS and a democratization of web languages. I however dread the day I get to read a full-stack C/C++ webpage.

gridlockd 6y ago
You can give WASM access to the DOM. What you describe is already possible, but most language runtimes are too big to be served for a website.
- rowanG077 6y ago
  Are there efforts to cache runtimes? I imagine most programs would be rather small if you don't have to ship the runtime.
  - gridlockd 6y ago
    There isn't really a good workflow regarding dynamic linking and libraries in WASM right now, but things are moving. Even then, what are the odds that your new user already has the particular version of your runtime cached already? If you really have a non-trivial application, then downloading the runtime isn't that big a deal I guess. If you just have a website, it wouldn't be warranted. Having said that, if you're careful, you can use Rust[1] or C/C++[2] with minimal overhead. I doubt that's going to become popular though. [1] https://www.hellorust.com/demos/add/index.html https://www.hellorust.com/demos/add/index.html [2] https://floooh.github.io/sokol-html5/index.html https://floooh.github.io/sokol-html5/index.html
    - rowanG077 6y ago
      Well the chances are low if it's the first time he is visiting my site. But since this will be used for web apps the chances are very high that a user will revisit.
      - gridlockd 6y ago
        That case is already covered by browser caching.
dep_b 6y ago
You can get a full-stack .net webpage with Blazor already
- tasogare 6y ago
  I’ve been playing with it in the last two days, and while it’s a bit annoying to have to deal with CSS for UI instead of XAML and the recompilation cycle, the framework is impressive. A lot of things can be done without touching JavaScript directly, and when in need the interop works well.