4 ms·
Yay, now all the bloat of .NET can spread into the browser too! </s> Seriously, I'm saddened to see all this overwhelming hype and "excitement" --- I am a deve
by userbinator 8y ago
Yay, now all the bloat of .NET can spread into the browser too! </s>
Seriously, I'm saddened to see all this overwhelming hype and "excitement" --- I am a developer myself, and just don't get it: I have used .NET apps before, and I could immediately tell it was such just from the speed (or lack thereof) and memory consumption --- the difference is obvious. It's the same with Java, which is not at all surprising. The absurd amount of object-oriented obfuscation I encountered in the few times I had to debug someone else's code in C# probably contributes to that too.
Taking over a second just to load an extremely simple app from localhost in the demo says all I need to know about this --- "no thanks". Please consider your users' experience...
- GiorgioG 8y agoYou have used .NET apps that were slow/mem consuming - have you ever considered that it’s the app developer’s fault? I can write a slow memory hogging app in C++ too. 1 second to load the whole app compared to the shitshow that is most SPA apps these days is a dream.
- pknopf 8y agoHaving two garbage-collected languages in the browser likely won't work out well.
- GiorgioG 8y agoWhat does having N-number of GC'd languages have any relevance? Your OS is an "app browser" with a variety GC language-based apps running happily alongside one another (Go, Java, C#, Elixir, etc)
- pknopf 8y agoYour OS is multithreaded, JavaScript isn't. Scrolling in your browser is bad enough when JS/dom has to many allocations.
- GiorgioG 8y agoWhat does WebAssembly have to do with JS? WebAssembly support for multithreading is in progress https://github.com/WebAssembly/design/issues/1073 https://github.com/WebAssembly/design/issues/1073 Look, you want to poo-poo on WebAssembly, that's fine, but the folks who build these browsers don't seem to be concerned enough about having GC'd langs running on their platform. Who has more at stake - you or them?
- pknopf 8y agoWebAssembly (currently) doesn't have direct access to DOM, so it has to use JS, hence the GC. Here is some of the JS for Blazor: https://github.com/aspnet/Blazor/tree/master/src/Microsoft.AspNetCore.Blazor.Browser.JS https://github.com/aspnet/Blazor/tree/master/src/Microsoft.A...
- pknopf 8y agoAlso, even when WebAssembly gets proper threading, .NET/Mono still uses a "suspend the world" GC mode which will still halt your execution. Nobody is poo-poo'ing anything. It is what it is. .NET just isn't likely to be a good fit for the browser for high-scale applications where performance is critical. I expect Rust to lead the way here.
- GiorgioG 8y ago> .NET just isn't likely to be a good fit for the browser for high-scale applications where performance is critical. I guess I don't understand what kind of 'high-scale applications where performance is critical' wouldn't be suitable for .NET but instead better suited to a systems programming language like Rust. If the bottleneck becomes the single-threaded JS interop, then what difference does it make which WASM language/runtime you choose as long as it's at least as fast as JS?
- pknopf 8y agoRust has no GC, .NET has a GC. Rust will be delivered with no runtime (minimal deployed size), Blazor will need the entire mono runtime and BCL.
- m_fayer 8y agoI was going to reflexively downvote this but it doesn't quite rise to the level of bad faith that I look for before I downvote. But, I'd ask you to recheck your impressions every couple of years, especially if a technology seems to be gaining popularity as opposed to dying. Stubborn and irrational corporate loyalty and manufactured hype are not the only reasons a technology stays alive, quality does play a role sometimes. .NET these days, especially with core, has a focus on power, performance, portability, and a sleek user experience. C# is a widely loved language that has a plethora of good stable tooling around it, and an intelligently evolving featureset that enables terse, expressive, functional-if-you-want-it coding. I think, like Kotlin, it's very well suited to writing "functional core, imperative shell" apps. You can also use it to write bloated J2EE-style lasagna-code, but no one's forcing you to do that. As for Blazor itself, it's similar to React/Vue/etc., but in C#. Writing complex frontend apps is hard even with TS and the big frameworks, and I can't think of why a new entrant with a statically typed language (with types at runtime!) that's still web-native would be a bad thing. As for startup time, hopefully they'll improve that, but you wouldn't use Blazor for a simple app anyway.
- userbinator 8y agoBut, I'd ask you to recheck your impressions every couple of years My most recent experience with a .NET application was within a day, and my impression has not changed since the beginning. (Although hardware has gotten faster...) Essentially every time I've had to use an annoyingly sluggish app that looks like a native one, I later discovered it was written in .NET . Despite all the claims of performance I have not once encountered an app that reflected those. It's never been "wow, .NET is so fast now?" but always "why is this so slow? ...oh, it's .NET." You can also use it to write bloated J2EE-style lasagna-code, but no one's forcing you to do that. That's the same non-argument the Java folks give. In theory it's possible to do better, but the language and culture naturally tends toward overengineering monstrosities because it is so much easier to do so when the language makes complexity easy to create. ...which brings me to the point I'm trying to make: your users don't care what fancy language or framework or whatever else you used. They care about the speed and (implicitly, since it affects speed) resource usage of your application, and that's what they'll notice.