News for hackers. Stuff that matters.
Re:Blazor Toast Notifications Using Only C#, HTML and CSS by rcarmo on Monday December 24, 2018 @06:35AM (#18751665)
I like the _idea_ of it, but watching one of the Blazor sample sites pull down 1.65MB of mono.wasm_plus_ nearly two megabytes of DLLs (from mscorlib.dll, System.Core.dll) is... sobering.

(Just go over to https://blazor.net/community.html, pick a demo and fire up your web inspector of choice)

For this to be practical, it needs a lot of trimming down, and I'm not sure how viable it is to do AOT and go through all the assemblies to do branch pruning before generating a cut-down WASM.

I do see a lot of appeal for enterprise scenarios and code reuse, and I guess there is a lot of potential there.

Re:Blazor Toast Notifications Using Only C#, HTML and CSS by s369610 on Monday December 24, 2018 @09:04AM (#18752175)
CoreRT is investigating wasm as a target. Discussion here about compatibility with blazor. In theory it should spit out much smaller binaries/bundles https://github.com/dotnet/corert/issues/4659
Re:Blazor Toast Notifications Using Only C#, HTML and CSS by sharpercoder on Monday December 24, 2018 @06:58AM (#18751756)
Since I presume these asm-compiled .NET BCL binaries are largely immutable, I think they can be cached aggressively. This means that the initial cost of downloading them may be high, but it browsers would support some kind of hashed asm library caching, this cost would be mostly one-off actions.
Re:Blazor Toast Notifications Using Only C#, HTML and CSS by jrs95 on Monday December 24, 2018 @07:59AM (#18751922)
We're also going to have widespread gigabit fiber and 5G soon, probably prior to significant adoption of technologies like this. So even if there is a period of time where these optimizations don't exist yet, rapidly improving internet speeds will help mitigate some of it as well.
Re:Blazor Toast Notifications Using Only C#, HTML and CSS by k__ on Monday December 24, 2018 @06:52AM (#18751725)
If they load these DLLs on demand, why not?

Companies will want to use their existing code-bases to make better SaaS offerings, Unity and Epic are already leveraging their C++ and C# engines.

I don't think too many people will start throwing new projects in the Web that are based on C#, Java or Go, 99% will be existing projects.

Probably Rust will make this race. It's more modern, no GC, almost C like performance and pushed by Mozilla who is THE company with the most Web know-how.

First it will eat the libraries and if they can flatten out the learning curve a bit, probably even the rest of the stack.

Re:Blazor Toast Notifications Using Only C#, HTML and CSS by mdpopescu on Monday December 24, 2018 @07:44AM (#18751874)
That's, like, an entire half a second man! /s

I am sure that the .NET Core team is not going to rest on their laurels with this technology; usually they are pretty good at optimizing stuff. Right now, it's only a proof of concept that's still in beta.

Re:Blazor Toast Notifications Using Only C#, HTML and CSS by pjmlp on Tuesday December 25, 2018 @12:27AM (#18756077)
Still way less of the image and auto play videos advertising junk many websites download.