News for hackers. Stuff that matters.

A comment on Mono and WebAssembly – Updates on Static Compilation. Parent comment

Re:Mono and WebAssembly – Updates on Static Compilation by j_s on Tuesday January 16, 2018 @03:23PM (#16162067)
Investigate a possibility to support JSX | https://github.com/bridgedotnet/Bridge/issues/808

Bridge.NET translates C# to JavaScript, but JSX is not currently supported.

[ Parent | on HN ]
Re:Mono and WebAssembly – Updates on Static Compilation by yodon on Tuesday January 16, 2018 @03:47PM (#16162363)
I like Bridge.NET but I’m not sure how they will survive once the current Mono WebAssembly tech hits release.
[ Parent | on HN ]
Re:Mono and WebAssembly – Updates on Static Compilation by kevingadd on Tuesday January 16, 2018 @07:41PM (#16164433)
WebAssembly does not cover use cases that require a ton of C#<->JS interop, and it may never adequately cover it. You end up needing a very complex interop bridge similar to C<->JS interop. A solution like Bridge can compile to JS, making interop near-zero-cost.
[ Parent | on HN ]
Re:Mono and WebAssembly – Updates on Static Compilation by yodon on Tuesday January 16, 2018 @09:40PM (#16165028)
Thanks for fantastic answer to my concern (for those who might object that kevingadd didn’t cite his sources, given his background he pretty much -is- a primary source)
[ Parent | on HN ]