Hacker News Reader

Comment by CyanLite4 | Hacker News Reader

I don’t know about you guys, but .NET Core (c#) and Visual Studio along with Blazor on the front end and deploying on Linux is pretty darn cool and highly productive. I haven’t had much success getting as productive on Python, Golang, or Node. Blazor eats TypeScript for lunch. Sometimes people confuse complexity for productivity. You can’t tell me installing 60,000 NPM packages just to have one dependency break is your idea of fun.

View on HN

I strongly believe that .NET Core/C# + VS2019 is easily the best option for productively shipping business features right now.

We also just started working with Blazor in production. There are still some rough edges in my opinion, but the conceptual model is very powerful. We currently use it in a limited internal system w/ server-side hosting model.

I do not think Blazor is an ideal technology for hosting netflix-scale applications, but for those highly-interactive/evented interfaces that you use for various business administration duties and expose to 10-10000 users, it's absolutely perfect. Being able to directly call C# business logic and subscribe to CLR events from your view logic is much more empowering than being forced to suck JSON through a straw, hoping client/server contracts are still lined up, and praying that all your complex XHR/websocket logic is pristine regarding error conditions and retries. Also, absolutely no NPM bullshit is required. I don't even have NodeJS installed on my machine anymore. All the javascript you will ever need can probably fit in a single static file. Our JS blazor interop shim is ~120 lines and it handles some incredibly complex client-side duties (get client rect for positioning elements server-side, subscribing and unsubscribing to events, etc).

JS dev here, I'd just like to say that the final sentence is just plain wrong at this point. Package locks are a thing and I don't actually remember the last time my project broke without myself having been behind the change that did it. My setup is actually pretty stable so new packages are pretty much never added either.

I've got used to the fact that outsiders aren't ever up to date with whatever is happening on the front-end.

Nobody ever seems to remark on how most UIs these days manage to be incredibly complex compared to how often they crash. Whereas if you look at older software or OS GUIs, the simplicity is astounding while still having more crashes. The point being that despite the bad rap that frontend dev gets, it’s actually made progress on the UI development front that is pretty much unrecognized.

I totally agree with you, but production deployments are terrible. The confusing way to handle secrets and environment variables, the lack of a standard database migration tool that is not tied to EF, the lack of a good standard integration layer with nginx... it's just a pain if you don't have a dedicated devops team.

Yeah that’s always been the big weakness in my experience. MS does offer a great developer experience but the deployment experience is still a long way behind Java and Go. Slowly moving in the right direction but windows containers are still a 2nd class citizen for example.

Oh and don’t forget Microsoft will probably sunset your chosen framework (such as WPF) and the 3rd party OSS ecosystem is much smaller. Oh and round here dotnet roles pay less, the final nail in the coffin for my MS dev experience!

Are people really using Blazor in production? What does your build pipeline look like? What dependencies/frameworks are you using?

I'm no way expert in Blazor but I wrote small post of how I setup Blazor Web Assembly using Github actions to Digital Ocean - https://www.integrated.ee/posts/dotnet-blazor-github-actions...

Yup. For a large desktop LOB app. Had to reinvent a few wheels because Blazor is so young (have high hopes to open source some of that). Build automation is a lot simpler for desktop-world. We do wish the framework and community were more mature, but are nevertheless very pleased with our decision.

.NET + visual studio + r# is the godlike stack. Haven't tried blazor yet but even asp.net is years ahead of the node ecosystem.

I'd say .NET Core with Jetbrains Rider is even better. :)

I am super excited to try out Blazor as well. I believe its the basis of the Azure web platform frontend so anyone can try it out just by signing up to the free tier. For me, I'm looking at rapid web ui prototyping. The ability to deliver a native-feeling web experience to a client in mere hours ;)

I'm interested in trying the .NET Core and Blazor stack.

However, "Visual Studio" is not my idea of the ideal developer experience... Maybe if the projects could be developed in VSCode

https://docs.microsoft.com/en-us/aspnet/core/blazor/get-star...

I tried out Blazor when it first came out. I really liked it! But at the time it wasn't quite production ready. Has that changed?

How does blazor deal with the situation if one client accidentally or maliciously triggers code that eats up CPU?

I'm also highly interested in any other information about your setup!

So I guess I should stop doing everything else and adopt a brand new M$ tech that totally blows out of the water what M$ offered a few years ago, which M$ said totally blows out of the water what M$ offered before that.

Got it.

It isn’t 1999 on Slashdot anymore. Using a dollar sign on a site dedicated to an ecosystem surrounding venture capital and all its friends just makes you look hilariously out of touch.

Yeah, poo on Microsoft for being a successful capitalist entity, said the community of people who work for, want to work for, or find a living supporting FAANG or the advertising and VC ecosystem propping it up.

Reply on news.ycombinator.com