Live data from Hacker News

.NET 10

devblogs.microsoft.com

21–30 of 605 posts

Re: .NET 10

#21
>I wish .NET was more popular among startups, if only C# could get rid of the "enterpisey" stigma.

I love C# and .NET and I use them extensively but I dislike the fact that the framework still kind of forces you into OOP.

If you like to have a more functional workflow you have to roll your own stuff or wrap objects in functional constructs.

But .NET is excellent for startups because:

-it is very fast to develop in

-has excellent tooling

-it is batteries included

-generally you have ONE way to do things that is accepted by most developers

-documentation is very good

-it supports large codebases with ease

-community is large enough

-you can use it for many areas, from embedded, to high performance computing, to desktop, mobile, web backend and web frontend

-it is performant

Re: .NET 10

#22
post #16

How come this quickly fell off main page and is ranked 395 right now? Don't know how trustworthy is this but it seems like it never was on top30: https://hnrankings.info/45888620/ This has 74 upvotes and posted 16hrs ago.. @dang?

Literally just got yoinked up from rank 199 to 2.

https://hackernews.life/?s=top&id=45888620&t=1762939537

It arrived at rank 86:

https://hackernews.life/?s=top&id=45888620&t=1762876085

Re: .NET 10

#23
post #18
post #15

Earlier quoted context omitted.

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

OpenAPI and client generators solve this issue easily.

No, that's not true. If you share code like this then you can do things like put the same validation code in the frontend and the backend: frontend to give a nice user experience, and backend to protect the endpoint.

Re: .NET 10

#24
post #18
post #15

Earlier quoted context omitted.

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

OpenAPI and client generators solve this issue easily.

Or GraphQL.

Still one lang on both ends is nice: there are some bits of code you want to run on both ends (like templating for SSR/SEO/caching; but also using them in the browser).

Re: .NET 10

#25
post #18
post #15

Earlier quoted context omitted.

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

OpenAPI and client generators solve this issue easily.

Still more work than just running the same code everywhere.

Re: .NET 10

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

Re: .NET 10

#28
That's a lot of goodies in a new release! It seems it is outpacing the JVM's development...

Re: .NET 10

#29

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…

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"?

Re: .NET 10

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

For what it's worth, the startup I currently work for is built entirely in C# and .NET, as was my previous employer. Both startups are based in the Dallas, TX area. Across both companies, applications were hosted on Azure and AWS using a mix of PaaS services and virtual machines running Windows and Linux. We've consistently found this stack to enable strong productivity and high-velocity release cadences.

At my current workplace we use a mix of on premise servers and Azure but at former workplaces we deployed to Google Cloud and AWS.
Post reply on HN