Live data from Hacker News

.NET 10

devblogs.microsoft.com

31–40 of 605 posts

Re: .NET 10

#31
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.

> I wish .NET was more popular among startups, if only C# could get rid of the "enterpisey" stigma. Too hard to ignore the benefits of cross-stack gains in Typescript/Python. The C# native phone, Blazor, etc just isn't quite there yet. Tried it at the last company, and full stack TS was just so much easier to do. The reality is that the vast majority of startups don't make it. The #1 thing startups should be focusing…

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

Re: .NET 10

#32
post #15

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.

While suffering the performance loss of V8 versus CLR, JVM or any compiled language.

One of the reasons I am back to writing more C++ code is C++ addons for node.js, as several SaaS products now only care about Next.js as extension SDK.

Re: .NET 10

#33
post #27

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.

C# Dev Kit, which VSCode pressures you to install, is a core very non-free component.

Re: .NET 10

#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!

Re: .NET 10

#35
post #29

Earlier quoted context omitted.

Rider is your option there, it's better than Visual Studio (I used to work on VS).

How is it so different than Visual Studio that you think it is "better"?

I switched over entirely to Rider as well, in my experience it's far more performant, has a far smoother UX, has a lot more functionality for power users, and includes Resharper by default, giving you access to a bunch more powerful inspections and refactoring.

Re: .NET 10

#36
post #29

Earlier quoted context omitted.

Rider is your option there, it's better than Visual Studio (I used to work on VS).

How is it so different than Visual Studio that you think it is "better"?

Offers essentially everything VS does + everything ReSharper does. I switched after years of using VS + R#, and have never looked back.

Re: .NET 10

#37

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!

What's wrong with System.Text.Json?

Re: .NET 10

#38
post #31

Earlier quoted context omitted.

> I wish .NET was more popular among startups, if only C# could get rid of the "enterpisey" stigma. Too hard to ignore the benefits of cross-stack gains in Typescript/Python. The C# native phone, Blazor, etc just isn't quite there yet. Tried it at the last company, and full stack TS was just so much easier to do. The reality is that the vast majority of startups don't make it. The #1 thing startups should be focusing…

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.

Re: .NET 10

#39

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!

Is it? We've switched over to System.Text.Json entirely.

Re: .NET 10

#40
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.

.Net is also good as a platform for other languages. I recently started working with RemObjects, and you can compile languages like Java, Swift, Go and more (VB, Pascal) to .Net. Then, the whole framework and ecosystem is available. I'm liking it a lot. They have customers who are startups and the 'got to have tools' folk like having lots of languages since they can onboard people who know anything-not-C# and benefit…

> they can onboard people who know anything-not-C# and benefit from the .Net library

I don't get this mindset. I'd much rather have the new guy spend a few months getting used to a new language, than have an organization where everyone uses different languages. It's a nightmare a few years down the road when you have 20 different projects in 15 different languages and the people who built them are mostly gone.

People are way too lenient with this stuff IMO. The goal of an organization should be to have one solution to each problem. For example we use .NET for backend and React for frontend. You don't need anything else. People love to talk about the right tool for the job, it's all BS. You can make pretty much any kind of website using react and pretty much any kind of backend using C#. The only reason to choose anything else is preference.

And sure maybe you have some data science people who need python, thats fine. Just don't have one guy using Py, another using R and yet others using Matlab. That's just asking for trouble. Pick one, stick to it. If you're going to make a change then migrate everything. If it's not worth that then the new tool probably isn't such a big deal after all.

Post reply on HN