←back to thread

.NET 10

(devblogs.microsoft.com)
536 points runesoerensen | 1 comments | | HN request time: 0.208s | source
Show context
jitbit ◴[] No.45888669[source]
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.

replies(28): >>45888799 #>>45888804 #>>45889332 #>>45891939 #>>45896032 #>>45898279 #>>45898305 #>>45898358 #>>45898503 #>>45898877 #>>45899062 #>>45899235 #>>45899246 #>>45899326 #>>45899445 #>>45899481 #>>45899858 #>>45900544 #>>45900791 #>>45900829 #>>45903218 #>>45904345 #>>45904435 #>>45905041 #>>45906073 #>>45907122 #>>45909149 #>>45909442 #
christophilus ◴[] No.45899326[source]
I really liked working with C#. I spent 15 years or so with it and found it very productive. But no; I don’t miss the culture of C# / Microsoft shops at all.
replies(1): >>45899411 #
mexicocitinluez ◴[] No.45899411[source]
> culture of C# / Microsoft shops at al

What do you mean?

replies(3): >>45900142 #>>45900245 #>>45907847 #
mohaine ◴[] No.45900245[source]
Been awhile since I've worked at one but it is usually grounded in trying to achieve 100% MS usage.

It is rarish to find a partial MS shop. Most of this is how hard MS makes it to use other tools. Even in 2025 they have good interop with external tools hamstrung.

Example: SQL Servers JDBC driver will convert an entire table's of data from ASCII to UTF and a full table scan instead of convertering your UTF bind to ASCII and using the ASCII based index. This doesn't break interop but does make it painful to code and one more reason to just use .Net.

replies(2): >>45901064 #>>45907883 #
1. oaiey ◴[] No.45907883[source]
There is no way a reasonable person would not deploy to Linux and postgres for cost reasons alone. No one wants to pay Microsoft or Oracle money for databases, operating systems or frameworks nowadays.