Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Asp.net Core updates in .NET 8 Preview 1

devblogs.microsoft.com

Post reply on HN
Print view View original

31–37 of 37 posts

Re: Asp.net Core updates in .NET 8 Preview 1

#31

Post by sebazzz »

Rapzid wrote: post #27
vyrotek wrote: post #2

Blazor United looks ambitious but sounds great! The goal feels similar to that of Remix.run and a few other frameworks that are blending SPA/SSR. I do wonder about the scalability of the Blazor Server mode which requires live and "sticky" SignalR connections.

Two main things have kept me away from Blazor: * Unclear state management story in Blazor WASM. There is a flux lib for Blazor but.. Ugh, I'm spoiled by MobX. Another project, Cortex.Net, inspired by MobX and uses Fody to make seamless fine-grain change subscriptions looked promising but the project did not gain traction :( * Unclear runtime extensibility: How can I "plug-in" Blazor components that were not present a…

- State management: not necessarily in my opinion. This is not React. Don't use tools you don't need, don't apply principles of completely different libraries. Work with cascading parameter and contexts instead.

- Runtime extensibility: you can do whatever you want in C# so you do you. In addition there is also DynamicComponent now, which is what I believe you are looking for.

Re: Asp.net Core updates in .NET 8 Preview 1

#32

Post by LeFantome »

lockhouse wrote: post #23
whalesalad wrote: post #22

Earlier quoted context omitted.

dev on .net is something I can understand ... but deploying and running windows servers in prod sounds like a hellish nightmare

The full .NET stack runs on Linux now. It’s even in RHEL’s repos. Heck you can even run MS SQL Server on Linux now if that’s your thing.

It is in Ubuntu and the AUR ( Arch ) as well.

In pragmatic terms, .NET is as native as anything else in Linux at this point.

You can even build it from source: https://github.com/dotnet/dotnet

In fact, the VMR ( linked above ) ONLY works on Linux at the moment with Windows and Mac support planned. So, .NET is Linux-first in some ways.

MAUI is not Linux first of course. The rest of it is becoming more and more Linux and container focussed though it seems.

Re: Asp.net Core updates in .NET 8 Preview 1

#33

Post by ducharmdev »

whalesalad wrote: post #22
vyrotek wrote: post #10

Earlier quoted context omitted.

The trick is to start the company yourself. :) We're 3 years in and full .NET stack. Is your project an internal app or public? I'm cautiously optimistic about Blazor Server but I'm not sure I like the sticky SignalR requirement. The expectation seems to be that the backend server will keep around a lot of state ( cough viewstate?) in memory associated to that session. It's a very convenient dev experience for sure,…

dev on .net is something I can understand ... but deploying and running windows servers in prod sounds like a hellish nightmare

Where I work, we all use MacBooks and deploy our services on Linux boxes. .NET has been cross-platform for years now.

Re: Asp.net Core updates in .NET 8 Preview 1

#34

Post by ducharmdev »

RagnarD wrote: post #16
avgDev wrote: post #6

I have been using Blazor Server for a project at work.....Honestly, it is so much better than using .Net MVC/Core with js sprinkled in. I developed stuff in java for android, swift for ios, and now mostly work in c#, SQL, .Net MVC/Core, blazor. Microsoft stack feels pretty good to me. Getting a start up job is a bit difficult, I came across two startups using microsoft stack and only one paid SV money. C#/.Net does h…

It's easy to start with, as I did, but do yourself a favor and move to Blazor Webassembly. Blazor Server handles UI events in a centralized way, and network lag really destroys the application. It might be ok on a fast and reliable intranet, but you really don't want to use it on the general internet. Standard Blazor Webassembly project setup creates a server side project and a client side one. C# code on the client…

The load times and lighthouse score for the MUD Blazor site has put me off of Blazor entirely for anything public facing:

https://mudblazor.com/

Re: Asp.net Core updates in .NET 8 Preview 1

#35

Post by bob1029 »

mythz wrote: post #24
avgDev wrote: post #6

I have been using Blazor Server for a project at work.....Honestly, it is so much better than using .Net MVC/Core with js sprinkled in. I developed stuff in java for android, swift for ios, and now mostly work in c#, SQL, .Net MVC/Core, blazor. Microsoft stack feels pretty good to me. Getting a start up job is a bit difficult, I came across two startups using microsoft stack and only one paid SV money. C#/.Net does h…

Blazor Server works well for low-latency Intranet Apps, it's stateful SignalR rendering circuit isn't suitable for laggy Internet Apps where deployments and long running Tabs results in users seeing frequent YSOD's. Which can be avoided with Blazor WASM that has different trade-offs with poor start times & SEO. Hopefully something that can be resolved with their upcoming Blazor United solution, which I'm assuming mea…

This is what we use it for. All of our internal admin/devops dashboards are built using blazor server. Employees on the east coast have the best experience, but no one in Texas seems to complain (server is in Virginia). We don't have any employees west of Austin, so latency works out fairly well for us.

Re: Asp.net Core updates in .NET 8 Preview 1

#36

Post by bob1029 »

I had a conversation on HN w/ a MS engineer last week about the System.Numerics improvements:

https://news.ycombinator.com/item?id=34793453

This stuff is super exciting to me. I've been using the SIMD-accelerated numerics for a side-project.

.NET8 is also an LTS version, so we are going to be upgrading to this for our B2B product sometime this year or early next. We had to skip over 7 due to our constraints, so we will be going from 6=>8.

Re: Asp.net Core updates in .NET 8 Preview 1

#37

Post by bob1029 »

easton wrote: post #5

I wonder if it'll be possible ever to do Native AOT if you rely on Newtonsoft (which is reflection heavy, last I heard). Yes, yes, I know, use System.Text.Json, but I already have all this code relying on Newtonsoft-y things :(

> but I already have all this code relying on Newtonsoft-y things :(

Welcome to the dungeon... Our jailer is polymorphic deserialization. We've got many gigabytes of Newtonsoft JSON in prod with that $type property throughout.

Any place I can use System.Text.Json I will, but there are a few legacy usages that absolutely won't work.

At this point, I'd like to rescind any expectation/desire for Microsoft to support polymorphic deserialization in their JSON library... It was a super powerful trick to get us to the next step, but it eventually turned into a nightmare for codebase maintenance.

Until we have this monster refactored, we won't be able to move most of our types into different namespaces or assemblies.

Post reply on HN