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

491–500 of 605 posts

Re: .NET 10

#491

Post by throw234234234 »

DarkNova6 wrote: post #462
bradford wrote: post #317

Earlier quoted context omitted.

I haven't kept aware of changes to Java in the last decade, but the things I didn't like about it then were: 1. The overall architecture (with the JVM) made it slower than the equivalent C# code. 2. C# really started embracing modern language features at a time when Java was kind of languishing (lambda functions, async patterns). Java seems like it's been in perpetual catch-up since then. (Not OP, disclaimer, I work…

Ah, got you. > I haven't kept aware of changes to Java in the last decade, but the things I didn't like about it then were: It's almost a shame. I am genuinely impressed with the gains the team has made in both, language aspects as well as JVM technology. They have some brilliant people working on it and I love to hear their talks (Brian Goetz and Mark Reinhold, mostly). But I suppose I would say the same about .Net,…

I've seen the gains in Java; the main things that would close the gap are not yet there in Java. .NET code, especially when tuned, still has significantly more knobs in your code to tune and make faster. An example would be proper generics with value types together means less boxing in generic code in general overall but there's a lot more I can think of. I've seen almost 50% of gains, particuarly when doing math like code, of moving away from Java to .NET especially if the jump to C/C++/Rust is too much for the team in question due to other requirements.

Re: .NET 10

#492

Post by [deleted] »

ikety wrote: post #104
tinyspacewizard wrote: post #42

Earlier quoted context omitted.

Start-ups should strongly consider F#. It's a force multiplier when you have a small team of strong developers.

F# seems really awesome. Used it briefly for an internal tool. Are you at a startup working with it?

[deleted]

Re: .NET 10

#493

Post by throwaway675867 »

xerxes249 wrote: post #206
ikety wrote: post #104

Earlier quoted context omitted.

F# seems really awesome. Used it briefly for an internal tool. Are you at a startup working with it?

I am working at a 2k fte company and we use F# for a lot, its very nice to work with, prefer Rider over Visual Studio though.

Similar for us in magnitude of sized company, maybe a bit bigger. Lots of services are F# (internal and main services), but we don't advertise it that much nor want to. Every time we consider switching (even to C#) the developers want to switch back even though C# is a fine language. Its not perfect, but its enjoyable to code in all the same. At this point the stack is battle tested.

Re: .NET 10

#494

Post by wvenable »

DarkNova6 wrote: post #464
wvenable wrote: post #316

Earlier quoted context omitted.

C# and Java might be similar technologies at some level but they not similar developer experiences at all .

How so? It striked me that the .Net library and Java frameworks like Spring or Quarkus are virtually identical.

There's more to developer experience than that. Your comment even demonstrates one of the differences: The .NET library compared to a bunch of different Java frameworks.

Re: .NET 10

#495

Post by sakesun »

catlover76 wrote: post #4
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.

> 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…

I saw a number of key .NET team members use Rider in Youtube videos.

Re: .NET 10

#496

Post by rajamaka »

Krastan wrote: post #455
rnewme wrote: post #449

Earlier quoted context omitted.

It literally puts food on your table?

Does it? If it didnt exist my company would need to develop it which still puts food on my table.

In fact it probably would put more food on your table.

Re: .NET 10

#497

Post by kkukshtel »

jcmontx wrote: post #136

I've worked with .NET for over 10 years and we built our startup on top of it. Here are my thoughts: Pros: * Stability * Very decent standard library * Good balance between productivity and robustness * Great package management * Extremely easy to upgrade, so essentially free goodies (performance) every year or so Cons: * Very MSFT dominated (obviously) * Subpar tooling outside of Windows (I'm looking at you C# Dev K…

I don't think C# really has bloat — there is generally very little overlap between things they add, and each release they don't add a lot. This release's big thing was better extension method syntax and the ability to use "field" in properties. Each release is about that big, and I feel like the language is largely very easy to internalize and work in.

New features are often more likely to be semantic sugar instead of some new big thing.

Re: .NET 10

#498

Post by kkukshtel »

Something great about this release as well is the release of "file-based apps"

https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals...

Basically, you can now write scripts in C# without the ceremony of a solution or project file — writing some code in a cs file and running `dotnet run myFile.cs`will execute the file directly.

You can also shebang to make it directly executable!

Hoping this inspires more people to give C# a go — it's incredible these days. Come in, the water is fine.

Re: .NET 10

#499

Post by jswny »

maccard wrote: post #178
jcmontx wrote: post #136

I've worked with .NET for over 10 years and we built our startup on top of it. Here are my thoughts: Pros: * Stability * Very decent standard library * Good balance between productivity and robustness * Great package management * Extremely easy to upgrade, so essentially free goodies (performance) every year or so Cons: * Very MSFT dominated (obviously) * Subpar tooling outside of Windows (I'm looking at you C# Dev K…

I use rider on Mac (and windows to be fair) and i think the experience is better than visual studio on windows. My biggest gripe with dotnet tooling is dotnet format. It’s not quick enough to use on a pre commit hook, so people don’t run it regularly and we get failures for it. It’s such a small nit, dotnet is a great environment to work in

Dotnet format is truly slow and bad. I wish the team focused on improving it, and working on better LSP support
Post reply on HN