Live data from Hacker News

Performance Improvements in .NET 6

devblogs.microsoft.com

81–90 of 256 posts

Re: Performance Improvements in .NET 6

#81
post #40

.NET 5.0+ drops the 'Core' from the name. The whole .NET platform has improved incredibly within the past 5 years. Previously, to run a C#/.NET app you would need Windows, Visual Studio, and a license for IIS. These days, you can run .NET entirely on Linux, without ever touching Windows or Visual Studio. (Founder here) At Amezmo [0], we've supported .NET for sometime now, and recently added .NET 6 as an option for ou…

You can, but if you actually start .NET on Linux without Windows and Visual Studio, you're not going to have the best experience. Lacking the background knowledge of the old .NET framework and how VS works was a consistent pain - both when reading outdated documentation and when getting help on something.

I'd recommend it to a Windows dev who wants to go crossplatform, but never to a crossplatform dev.

Re: Performance Improvements in .NET 6

#82
post #39

WinForms and its Visual Studio designer are still broken, WPF is still riddled with bugs and was declared obsolete in ~2017 in favor of UWP, UWP is marked obsolete in favor of WinUI, and WinUI's OSS release was postponed just two days ago because it's not ready. Microsoft is marketing .NET 6 as the replacement for .NET Framework but you still cannot properly do desktop UI with it. I honestly don't understand why they…

Couldn't agree more. Microsoft lost their minds on the UI / desktop app side - which was a core strength (historically). WinForms was fine / great / amazing. 90% of business / line apps could be handled with it. I have no idea how / why it's taken them so long and they STILL have not gotten their replacement story straight for it and they regressed the designer in .NET. Did they just lose their minds there? Hire a bu…

UI component design is extremely difficult. It's at the intersection between UI design and API design, both difficult disciplines in themselves. It doesn't help that it has traditionally been mired in OO hype sauce.

Re: Performance Improvements in .NET 6

#83
post #59

and we're stuck with Java. Sad, I hope that bigger companies and startups choose to use .NET for the future. I love it but can't it seems like 80% of the big tech companies here are using java

I like the uniformity of Java language. I like the "inner class" feature that has to be manually emulated in C#. I also like that I can implement anonymous abstract class-interface ad hoc in Java. I wish that internal visibility in C# was tied to a namespace instead of assembly, like package visibility in Java. Method co-/contravariance in C# is tied to interfaces. I prefer it tied to individual methods, like in Java…

> (...) What they did with streams kind of signals that they want to deprecate them in the long run. It's a missed innovation opportunity.

Do they? They kept evolving the Stream API after Java 8 well into Java 16 (Stream::multiMap, Stream::toList, etc.), it doesn't really seem to me like this is true.

Re: Performance Improvements in .NET 6

#84

Earlier quoted context omitted.

Is there a UI story that doesn't suck?

The command line. (Hey, you said UI, not GUI.) Or for all its faults on macOS, SwiftUI on the iPhone is pretty good. And depending on your angle of view, depending on the kinds of UI you're attempting to make, you could argue that the UI story of HTML5 is able to not suck if you have the self-discipline to avoid the sucky things.

> The command line

I can think of no shortage of frustrating CLI experiences.

There is no perfect library that solves for all possible problems. Pros and cons and all that. I'm pleasantly happy with all modern UI frameworks across major OSes and HTML5 options. I have so many things to be thankful for complaining about.

Re: Performance Improvements in .NET 6

#85
post #40

.NET 5.0+ drops the 'Core' from the name. The whole .NET platform has improved incredibly within the past 5 years. Previously, to run a C#/.NET app you would need Windows, Visual Studio, and a license for IIS. These days, you can run .NET entirely on Linux, without ever touching Windows or Visual Studio. (Founder here) At Amezmo [0], we've supported .NET for sometime now, and recently added .NET 6 as an option for ou…

Got this "Access denied | www.amezmo.com used Cloudflare to restrict access" (from India)

Re: Performance Improvements in .NET 6

#86

Earlier quoted context omitted.

F# is cool, but definitely not where to start. C# is by far, by far, by far the most popular .net language

Depends on what OP is familiar with. If they know/like functional programming, I'd recommend F# highly. If not... Yeah go with C#. Then later learn F# because it's absolutely kick ass :)

An experienced functional programmer can learn F# in a minute, which is fine for console programs. But I tried to write a basic GUI program in F# on Linux and gave up after I reached my googling limit.

Re: Performance Improvements in .NET 6

#87
post #48

Earlier quoted context omitted.

The UI story on Windows is completely broken but that has been the case forever. Has MS basically released anything sustainable on the UI side since MFC? It feels like they’ve constantly provided a new new replacement every few years that replaced the new replacement from a few years ago since then.

That's definitely true but they did a good job supporting their tech once it was released. My company has been using WinForms on .NET Framework for over 10 years now and it's working really, really well. Microsoft even added HiDPI support to it. When Microsoft announced they wanted to bring WinForms to .NET Core 3, we were initially very happy as it meant we could switch to .NET Core. But then they did all kinds of s…

I had a lot of problems adding HiDPI support to a moderately complex WinForms application. It was a huge time sink.

Re: Performance Improvements in .NET 6

#88
post #39

WinForms and its Visual Studio designer are still broken, WPF is still riddled with bugs and was declared obsolete in ~2017 in favor of UWP, UWP is marked obsolete in favor of WinUI, and WinUI's OSS release was postponed just two days ago because it's not ready. Microsoft is marketing .NET 6 as the replacement for .NET Framework but you still cannot properly do desktop UI with it. I honestly don't understand why they…

What are you talking about? WPF is still supported and a viable way to implement UI components. Same for WinForms. UWP never replaced them. What they are doing with WinApp SDK and WinUI is to extract features that were packaged with UWP to make them available to any type of Windows application.

Xamarin is also still a thing, MAUI will be a thing in the future, Uno is another option, Avalon too. There is a lot of options for .Net GUI, most of them are mature and maintained.

Re: Performance Improvements in .NET 6

#89

Earlier quoted context omitted.

I'm mostly doing my UIs in Qt and I'm always happy, sure it's not perfect but it consistently allows me to do what I want in a cross-platform way with minimal effort (especially when I compare with the royal empirical pain that is webdev)

For windows what's your hello world workflow / stack. I've wanted to get into QT, but there seem to be a bunch of different flavors out there. I'm more a winforms guy then an HTML/XAML/CSS type person.

On Windows, there are two easy ways to get started: Qt Creator and the Qt Addin for Visual Studio. Qt Creator is easier, I think. Personally, I use Qt Widgets a lot and ignore Qml, because the later has seemingly much less powerful widgets out of the box.

Re: Performance Improvements in .NET 6

#90
post #78

Earlier quoted context omitted.

The UI story on Windows is completely broken but that has been the case forever. Has MS basically released anything sustainable on the UI side since MFC? It feels like they’ve constantly provided a new new replacement every few years that replaced the new replacement from a few years ago since then.

> Has MS basically released anything sustainable on the UI side since MFC? MFC is nothing more that a C++ GUI library wrapping the Windows Win32 GUI layer. The problem with that Win32 GUI is it has not changed for several decades, which is why any application using that Windows GUI layer looks old and outdated on modern Windows. Since Microsoft is not updating the Win32 GUI layer, it is basically obsolete. However so…

[deleted]
Post reply on HN