Re:Blazor Toast Notifications Using Only C#, HTML and CSS
by untog on Sunday December 23, 2018 @11:15PM
(#18750286)
IIRC, Rust is often chosen because you don't have to embed a garbage collector with your code. That's not the case with Go (or C#)
[ Parent
| on HN ]
Re:Blazor Toast Notifications Using Only C#, HTML and CSS
by pjmlp on Monday December 24, 2018 @05:56AM
(#18751563)
WebAssembly roadmap plans to add GC support, so that is only an interim issue.
Re:Blazor Toast Notifications Using Only C#, HTML and CSS
by k__ on Monday December 24, 2018 @06:40AM
(#18751684)
While I had the impression that GC support means the will expose the JavaScript engine's GC to be used by other languages and I don't know if it would work for all, is the GC really such a big chunk of these runtimes?
Re:Blazor Toast Notifications Using Only C#, HTML and CSS
by oaiey on Monday December 24, 2018 @07:36AM
(#18751857)
.NET has the concept of pluggable GC since last CoreCLR release. I highly suspect that other runtimes will have the same.
I also have my doubts but more regards performance of a shared WebAssembly GC in regards to different runtimes.