I'd love to hear from some .NET fanatics, how would you convince someone to use that ecosystem over another?
I love .Net, but context is key. I may suggest .Net for new WebAPI development (minimalist or otherwise), typically with a deployment target of containers and or Linux. It is a strong web back-end language in a similar way to Java but with Linq support, async/await, and a better primary programming language (C#). It has strong integrations into corporate software and all popular DBMS. But, frankly, Linq is the magic…
.NET 8
81–90 of 374 posts
Re: .NET 8
#82Re: .NET 8
#83Earlier quoted context omitted.
With consistent, reasonable-by-default threading abstractions baked in
Are those new? What are they by name?
A garden variety of keywords is async/await, TPL (tasks/futures and structured concurrency) and PLINQ (Rust's Rayon).
Re: .NET 8
#84Earlier quoted context omitted.
- It is a mature platform with yearly updates. - New stuffs integrate nicely with existing features. - C# and F# gets yearly updates. - Somehow they manage to get the platform faster every year. - Microsoft Orleans.
Microsoft seems weird tho. They dont really support any recommended way to do .NET on Mac and you have to rely on Rider or half ass VS Code experience.
Re: .NET 8
#85Can I get an explanation of the relationship between .NET and Mono? I have vague memory of reading somewhere that Mono or maybe just MonoBuild was completely obsolete since everything was now open source in .NET. Does Mono still have a reason to exist? Is it all incorporated into .NET now? (btw, I still don't get why it's called .NET, and I don't know if assemblies are native code or bytecode wrapped in the same bina…
.NET can now do either one - you can ship PE bytecode and require the dotnet runtime, which works in practice similar to e.g. Python or Ruby (you run `dotnet ./myapp.dll`), or you can precompile it into a single platform-specific binary that is just a native code app, similar to Go's static binaries.
Re: .NET 8
#86I'd love to hear from some .NET fanatics, how would you convince someone to use that ecosystem over another?
You simply don't have to spend too much time researching what to do, just follow the docs and get started writing code and delivering features.
If you stray from the full integration of MS products, you start to lose some of the value proposition.
Re: .NET 8
#87Earlier quoted context omitted.
- It is a mature platform with yearly updates. - New stuffs integrate nicely with existing features. - C# and F# gets yearly updates. - Somehow they manage to get the platform faster every year. - Microsoft Orleans.
Microsoft seems weird tho. They dont really support any recommended way to do .NET on Mac and you have to rely on Rider or half ass VS Code experience.
Re: .NET 8
#88Earlier quoted context omitted.
At least until it gains an immense market share and Microsoft starts monetizing it again. They've already tried in .NET Core 7, no? I'm staying away for now.
Can you share any details about .NET Core 7's monetization? I couldn't find anything on Google.
Re: .NET 8
#89Earlier quoted context omitted.
Are those new? What are they by name?
I think the parent comment is talking about System.Threading.Tasks. I might be wrong though.
Re: .NET 8
#90Earlier quoted context omitted.
At least until it gains an immense market share and Microsoft starts monetizing it again. They've already tried in .NET Core 7, no? I'm staying away for now.
Can you share any details about .NET Core 7's monetization? I couldn't find anything on Google.