Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

.NET 8

devblogs.microsoft.com

Post reply on HN
Print view View original

61–70 of 374 posts

Re: .NET 8

#61

Post by declan_roberts »

xeromal wrote: post #4

Tangentially related but I was impressed with .NET recently. I was recently tasked with tackling an extremely old and proprietary video format that embedded GPS, video, audio, and several other components. The files were huge and just a mess to understand and I eventually found an old player application that was also proprietary. I decompiled it into C# and stripped the player aspect out of it leaving the code the pe…

Backwards compatibility is something they take really seriously in the enterprise world, but something thrown out the window in the rest of the industry.

Re: .NET 8

#62

Post by Mountain_Skies »

pdntspa wrote: post #11

I just wish its cross-platform UIs weren't such a mess. Particularly with its MVCish implementation, it was like it couldn't decide what it wanted to be. I really really wish there was a good, straightforward desktop GUI for .Net that simply worked crossplatform and wasn't a complete pain in the ass to program.

The Windows only desktop UI is a huge mess too. It reminds me of Babbage and his Difference Engine that could never be finished because part way through, he'd come up with "even better" ideas and start a new one.

Re: .NET 8

#63

Post by Someone1234 »

willsmith72 wrote: post #20

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 that makes .Net special.

Otherwise, for new development, I'd pick something else for creating user interfaces. Like Electron on the desktop and a popular TypeScript based JavaScript framework De jure on the web (utilizing WebAPI in .Net behind the scenes).

Re: .NET 8

#64

Post by oaiey »

martindevans wrote: post #52
jordigh wrote: post #13

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

There used to be .NET Framework (which was a Windows only runtime built by Microsoft) and Mono (an open source implementation for various other platforms). In 2016 they started building .NET Core which is new open source implementation (built mostly by Microsoft) which runs on more platforms. For a while all three existed side by side. Eventually .NET Core caught up and overtook the other implementations. These days…

While correct, modern .NET supports currently two VM: CoreCLR and MonoVM. The later mainly as AOT compilation target for iOS, Android and WebAssembly. Mono is still better suited for that, but the AOT compilation of CoreCLR is progressing.

I think there is nothing else left from the Mono project like the class library or the compiler/toolchain.

Re: .NET 8

#65

Post by topbanana »

mathverse wrote: post #55
dodyg wrote: post #44

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

What's wrong with Rider?

Re: .NET 8

#66

Post by collaborative »

creshal wrote: post #22
pdntspa wrote: post #11

I just wish its cross-platform UIs weren't such a mess. Particularly with its MVCish implementation, it was like it couldn't decide what it wanted to be. I really really wish there was a good, straightforward desktop GUI for .Net that simply worked crossplatform and wasn't a complete pain in the ass to program.

In their defence, does any other language have one, these days? The landscape hardly looks good, which is how electron et al. got so popular to begin with.

Java and Python have a few. I still don't get how electron got so popular. It's always been pretty straightforward to ship an app with a self-contained Java runtime, much the same as electron ships with v8. Java GUIs have always been worse than c++ ones, but still.. much better than electron I'd say

Re: .NET 8

#67

Post by dodyg »

ryanjshaw wrote: post #54
klauserc wrote: post #6

Apart from the very welcome QoL features in C# 12 (collection literals, primary constructors for ordinary classes), the "Aspire" announcement is very interesting. Haven't decided yet if its a good thing or too much "magic".

Kind of annoyed - I just spent the past week getting familiar with Dapr, and now there's Aspire which seems to have similar goals and is also funded by Microsoft: the Azure CTO even wrote the introduction to the Dapr for .NET Developers book! And of course the Aspire announcement makes no mention of Dapr - I wonder if the teams have even spoken to each other!

I was asking about Orleans integration. They are working on it (https://twitter.com/reubenbond/status/1724463381686686075).

I think it's a matter of time for Dapr stuff to be integrated. It is after all the first preview.

edit: here's more info about Dapr and Aspire

https://learn.microsoft.com/en-us/dotnet/aspire/reference/as...

Re: .NET 8

#68

Post by endianswap »

haolez wrote: post #49
financltravsty wrote: post #8

Lots of very cool stuff here (AOT, Aspire, etc.). .NET has been held down by the image of its early days, but it has become a pure joy to work with recently. The improvements in tooling and ergonomics have made it a replacement for Go in our org (we migrated from .NET Core 3.1 to Go back to .NET 6 recently).

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

#69

Post by willsmith72 »

SideburnsOfDoom wrote: post #34
willsmith72 wrote: post #20

I'd love to hear from some .NET fanatics, how would you convince someone to use that ecosystem over another?

As a long-term happy .NET user; you should use what makes you happy.

fair enough, I'm happy with what I've used through my career, but I've never been in a situation using .NET and only tried a hello world.

I think you can always learn something from trying totally different tech, so i'm game to try it for a personal project, but want to hear what people love about it so I can dig in the right direction.

Re: .NET 8

#70

Post by Someone1234 »

strich wrote: post #48
pdntspa wrote: post #11

I just wish its cross-platform UIs weren't such a mess. Particularly with its MVCish implementation, it was like it couldn't decide what it wanted to be. I really really wish there was a good, straightforward desktop GUI for .Net that simply worked crossplatform and wasn't a complete pain in the ass to program.

I would say Blazor is really very very good now. One of the most awesome things about it is that your skill with it transfers almost directly between a desktop app, web API, or web site. All the code is almost the same.

Blazor is just history repeating itself. This is Web Forms with a shiny coat of paint and the "magic" this time is WebAssembly and a different proprietary web interface that is undebuggable.

I've heard this "Microsoft has finally created a completely cross platform UI framework" like twenty times...

Post reply on HN