Live data from Hacker News

.NET 8

devblogs.microsoft.com

271–280 of 374 posts

Re: .NET 8

#271

Earlier quoted context omitted.

> .NET has been held down by the image of its early days, but it has become a pure joy to work with recently People have been saying that for the past 4 years. As someone who's never used .NET but develops embedded apps for Linux, I had high hopes for it become the best story for crossplatform development, it still feels like the crossplatform is held by ductape. It's still Xamarin for mobile, Avalonia (a 1-man proje…

This is not a .NET problem. There really isn't a simple way to do cross platform (Windows/Linux/macOS) UIs with any language. The least bad option is to make it a web page, maybe wrap it with Electron.

Livecode does the cross platform thing

Re: .NET 8

#272
post #182

Blazor actually looks compelling now that it has server side streaming and rendering, as well as component level interactivity. Once .NET is integrated with the new WasmGC features, it will get even better! (I don't think they mentioned WasmGC on the roadmap but I can bet anything they're going to do it).

You can find .NET's position on the WasmGC spec here: https://github.com/dotnet/runtime/issues/94420 .

Thank you!

Re: .NET 8

#273

Earlier quoted context omitted.

pySide6 has been a dream for me, it 'just works' and QT is quite robust. I am currently fucking with Java via GraalVM, and packaging my app for distribution has been absolute hell: jlink throws errors. jpackage somehow gets stuck in an infinite loop that generates a directory tree of seemingly infinite depth (so deep that even Explorer can't delete it) GraalVM native-image can't complete and throws all sorts of weird…

Not sure if it suits your use case, but the best I have experienced is jDeploy

Interesting... I like how it piggybacks off npm

Re: .NET 8

#274
post #235

Earlier quoted context omitted.

Wasn’t there some issue with debugger on Non-Windows platforms?

The issue that it is free as in beer but not open source as in MIT.

I think you mean open source as in GPL, given that MIT doesn't force to give the source code, hence why it is beloved for commercial products.

Re: .NET 8

#275
post #111

I'm looking at a language to write simple executables with or without GUI and that are not too verbose or too complicated. A bit like a compiled python :) Would .NET 8 be a good challenger ? I previously didn't consider it because the compilation to binary was looking more like an experiment, and the example I've seen were quite verbose (in a java way).

Go seems like a good fit for that.

It seems to be the more mature language for my use case. How is the GUI development and C++ interop ?

Re: .NET 8

#276
post #49

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

There is no such thing as .NET Core 7, “Core” was a temporary distinction when the Windows-only . NET Framework was still being actively developed, retired with the consolidation to a single .NET with .NET 5. If you got .NET Core 7 somewhere, I’m sure it is monetized: that's often the point of a scam.

As someone that knows .NET since it was only available to MSFT partners, I find quite valuable the Core and Framework suffixes, especially when discussing with people not versed in the .NET history, as many people get confused why .NET 4 isn't compatible with .NET 7 for example.

Re: .NET 8

#277

I'm looking at a language to write simple executables with or without GUI and that are not too verbose or too complicated. A bit like a compiled python :) Would .NET 8 be a good challenger ? I previously didn't consider it because the compilation to binary was looking more like an experiment, and the example I've seen were quite verbose (in a java way).

It depends... .NET 6 was already capable of most things you are looking for, but there are some limitations. I personally think it is a really versatile language and if you know it, you can get the most things done somehow. I wrote a little cross platform C# command line tool called `tone`[1] for tagging audio files and it compiles via github actions for windows(x64), linux(x64,arm64,arm6,arm7), macOS (x64, arm64) as…

I would target the main desktop, and maybe raspberry and android but it's very far from my horizon and not a criteria.

I was thinking that flutter is a dart library/framework ? How is it compatible with C# ?

Re: .NET 8

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

The compatibility shims that come implicit with .NET are incredible. In my experience many of the .NET Framework libraries work right out of the box on .NET (Core), even on Linux.

Re: .NET 8

#279

I'm looking at a language to write simple executables with or without GUI and that are not too verbose or too complicated. A bit like a compiled python :) Would .NET 8 be a good challenger ? I previously didn't consider it because the compilation to binary was looking more like an experiment, and the example I've seen were quite verbose (in a java way).

It would. Compiling .NET binaries to a single executable that does not require installing a runtime has been a thing for quite some time actually, but NativeAOT definitely improves the "simple and lightweight" part of your inquiry: JIT: dotnet publish -p:PublishSingleFile=true -p:PublishTrimmed=true AOT: dotnet publish -p:PublishAot=true

Looks interesting! Does nativeAOT works for GUI ?

Re: .NET 8

#280
post #50

Earlier quoted context omitted.

Are those new? What are they by name?

.NET has had first-class parallelism and async/await since around .NET Framework 4.0 release which was...13 years ago huh. There have been many improvements in the underlying runtime since then though. A garden variety of keywords is async/await, TPL (tasks/futures and structured concurrency) and PLINQ (Rust's Rayon).

In addition to the base TPL (System.Threading.Tasks), IAsyncEnumerable in recent .NET versions has deepened and simplified even more useful concurrency patterns (Async Generators), especially when paired with Ix.NET (System.Interactive.Async) which adds a lot more LINQ/PLINQ operators, many of which are designed to intentionally mirror ReactiveX.NET (System.Reactive), the even older but just as useful push-based (IObservable) relative of IAsyncObservable.
Post reply on HN