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

.NET 10

devblogs.microsoft.com

Post reply on HN
Print view View original

41–50 of 605 posts

Re: .NET 10

#41

Post by DeathArrow »

cebert wrote: post #15
phillipcarter wrote: post #10

Earlier quoted context omitted.

Is it though? Backends can be any language and there's a lot more variety there -- TS+node, Go, Python, Java. It's just .NET that's largely ignored for no real technical basis.

You can easily use the same types and libraries in your backend and frontend with TypeScript. It’s not at easy with dotnet.

>You can easily use the same types and libraries in your backend and frontend with TypeScript. It’s not at easy with dotnet.

You can do that in .NET, too if you use Blazor for frontend.

Re: .NET 10

#42

Post by tinyspacewizard »

jitbit wrote: post #2

For us, every .NET upgrade since .NET 5 has gone surprisingly smoothly and reduced CPU/RAM usage by 10–15%. We were even able to downgrade our cloud servers to smaller instances, literally. I wish .NET was more popular among startups, if only C# could get rid of the "enterpisey" stigma.

Start-ups should strongly consider F#.

It's a force multiplier when you have a small team of strong developers.

Re: .NET 10

#43

Post by monerofglory »

kurokawad wrote: post #34

To me, it's pretty much unbelievable that Microsoft introduces an agent framework while for JSON serializing third-party Newtonsoft is still the go-to. Edit. I was not aware that the gap between System.Text.Json and Newtonsoft narrowed, take my comment with a grain of salt, please!

The go-to nowadays is System.Text.Json, developed by the same person as Newtonsoft.Json, built in to .NET.

Newtonsoft.Json as the primary JSON serializer (at least in every place I've worked) has NOT been the case versus System.Text.Json for years. Though it certainly used to be the case.

Re: .NET 10

#44

Post by BitsAndObjects »

It’s exciting to see so much deep computer science that’s gone into optimising the language / JIT / GC / etc (inc. utilising hardware advances).

In a world obsessed with AI and web tech, this is a refreshing read!

Re: .NET 10

#45

Post by debugnik »

clintmcmahon wrote: post #13
catlover76 wrote: post #4

Earlier quoted context omitted.

> I wish .NET was more popular among startups, if only C# could get rid of the "enterpisey" stigma. There's that, but there's also the developer experience and functionality for people to run it on Mac and Linux. We have a small C# service that we run locally via Docker (which I think is usually the optimal setup anyways) and develop with VSCode. Since it's small, it has worked well. Would it work well if that was ou…

There used to be a Visual Studio for Mac (since retired) but they never could get it right in comparison to the Windows version. VS Code on a Mac works great and with the ability to run SQL Server in Docker you can have the old stack right there on your Mac.

They couldn't get it right because Visual Studio for Mac was actually a rebranded MonoDevelop, an entirely different IDE than Visual Studio.

Re: .NET 10

#46

Post by kurokawad »

monerofglory wrote: post #43
kurokawad wrote: post #34

To me, it's pretty much unbelievable that Microsoft introduces an agent framework while for JSON serializing third-party Newtonsoft is still the go-to. Edit. I was not aware that the gap between System.Text.Json and Newtonsoft narrowed, take my comment with a grain of salt, please!

The go-to nowadays is System.Text.Json, developed by the same person as Newtonsoft.Json, built in to .NET. Newtonsoft.Json as the primary JSON serializer (at least in every place I've worked) has NOT been the case versus System.Text.Json for years. Though it certainly used to be the case.

Uh okay! I was not aware of this. Thanks for pointing that out. Why is there so much difference in the NuGet downloads between both libraries tho?

Re: .NET 10

#47

Post by olavgg »

jitbit wrote: post #2

For us, every .NET upgrade since .NET 5 has gone surprisingly smoothly and reduced CPU/RAM usage by 10–15%. We were even able to downgrade our cloud servers to smaller instances, literally. I wish .NET was more popular among startups, if only C# could get rid of the "enterpisey" stigma.

As a startup, what is it in for me to switch from Java, Spring Boot, Hibernate, Beam, Flink, Pulsar, Vault, KeyCloak ecosystem to C#.Net? Is the documentation better? Do I get better performance? Is the community larger and more stable?

Re: .NET 10

#48

Post by bob1029 »

These improvements are really making me look forward to Unity finishing their CoreCLR conversion. I think this will be one of the more disruptive announcements once it's complete.

Re: .NET 10

#49

Post by forrestthewoods »

charcircuit wrote: post #38
pif wrote: post #31

Earlier quoted context omitted.

I wish people stopped conflating web programming with the whole realm of software development.

If you ignore Android / iPhone, where language choice is limited, practically all other development is web.

> practically all

Define “practically all”. I would accept “clear majority”.

But practically all? Nah. I mean the hot new areas for funding right now are AI and robotics neither of which are web!

I’m coming up on 20 years professional experience. Exactly none of it has been mobile or web! The programming field is so much bigger than HN likes to pretend.

Re: .NET 10

#50

Post by madarcho »

cies wrote: post #27
nozzlegear wrote: post #7

As a daily user of F#, I'm most looking forward to the support for "and!" in computation expressions. There are a few performance-critical pieces of code I can think of that are currently wrapped up in "Task.WhenAll" / "Parallel.ForEachAsync" that I'd like to extract back into "native" F# task computations.

I really like F# (as I like OCaml, Elm and Haskell); but I'm always afraid MS will kill it one day. It helps that now most (if not all) parts of the stack are open source and run on Linux.

Where is this worry coming from? (I'm curious, not shutting it down)

I might be biased from having worked with production F#, but it feels more like functional is making its way into C#, as the general industry sees value in functional principles. So F# feels like its more here to stay?

Post reply on HN