Performance Improvements in .NET 6 • Hacker News Board

Re: Performance Improvements in .NET 6

#171

Post by bigbizisverywyz » Fri, Aug 20, 2021, 12:19 PM UTC

jcelerier wrote: post #92

whoknowswhat11 wrote: post #74

Earlier quoted context omitted.

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.

I'll be honest I don't think that doing C++ on windows is a good idea. The language needs to do a lot of file access for includes, and on NTFS those are super slow, my builds on Linux are something like 1/3 of the time on windows (building the same software with the same commit of clang 12 and lld, same computer, same SSD). But if you don't want to install a Linux partition, then just use aqt to install Qt: https://g…

>The language needs to do a lot of file access for includes, and on NTFS those are super slow,

I'm not sure I'd blame NTFS as such - but you can massively improve build times by creating a precompiled header .pch include file in your projects.

Re: Performance Improvements in .NET 6

#172

Post by garrypettet » Fri, Aug 20, 2021, 12:21 PM UTC

tomnipotent wrote: post #56

addicted wrote: post #43

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.

Is there a UI story that doesn't suck?

I've been using Xojo (https://xojo.com) for about 15 years now to make cross-platform GUI apps. The language is similar to VB6 but it's been constantly updated. No affiliation, just a happy customer.

Re: Performance Improvements in .NET 6

#173

Post by Lobosque » Fri, Aug 20, 2021, 12:21 PM UTC

The problem with .NET Core is that while the runtime is truly multiplatform, the development experience is not.

The performance improvements on each release are trully impressive, but I think at this point the focus should go towards a better development experience.

Developing on VS Code is such a hurdle thanks to the Omnisharp language server that constantly crashes, and the project does not seems to be among MS top priorities for .NET platform.

Restarting the IDE every few minutes is very frustrating and hardly justifiable from a productivity point of view.

Re: Performance Improvements in .NET 6

#174

Post by coldacid » Fri, Aug 20, 2021, 12:24 PM UTC

Lobosque wrote: post #173

The problem with .NET Core is that while the runtime is truly multiplatform, the development experience is not. The performance improvements on each release are trully impressive, but I think at this point the focus should go towards a better development experience. Developing on VS Code is such a hurdle thanks to the Omnisharp language server that constantly crashes, and the project does not seems to be among MS top…

You don't have to restart the IDE. Usually you can just tell Omnisharp to reanalyze your solution and wait a few seconds for that to complete. If Omnisharp has actually crashed, this will start up a new instance, too.

It would definitely be nice if more resources were put towards making Omnisharp smarter and more stable, especially as it seems to be the premier implementation of an LSP server.

Re: Performance Improvements in .NET 6

#175

Post by tonyedgecombe » Fri, Aug 20, 2021, 12:27 PM UTC

stinos wrote: post #124

tonyedgecombe wrote: post #91

Earlier quoted context omitted.

I don't think anybody is expecting perfection. Personal I just don't want so much needless churn, especially on the .Net side. WPF in particular seemed to offer so much promise but was abandoned at birth. I now treat UI stuff from Microsoft the same way I treat services from Google, something to be avoided because it will probably be abandoned within a short period.

There's a major difference though: when Google abandons a service it is gone and you have to look for an alternative. When Microsoft 'abandons' WPF your 15 old application still builds and runs today and receives occasional updates like proper HDPI support.

That would be just about OK if it wasn't half baked in the first place.

Re: Performance Improvements in .NET 6

#176

Post by coldacid » Fri, Aug 20, 2021, 12:28 PM UTC

addicted wrote: post #43

foepys wrote: 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…

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.

MFC was sustainable?

Re: Performance Improvements in .NET 6

#177

Post by ygra » Fri, Aug 20, 2021, 12:37 PM UTC

DoingIsLearning wrote: post #114

notanaverageman wrote: post #111

Earlier quoted context omitted.

WPF is still Windows only. It will not work on a Linux machine.

Indees it seems to be a dead end. https://github.com/dotnet/wpf/issues/48 Thanks for clarifying.

For a WPF-like development experience that's also cross-platform, perhaps take a look at Avalonia: http://avaloniaui.net/. It's not a drop-in replacement, but very, very similar.

Re: Performance Improvements in .NET 6

#178

Post by ocdtrekkie » Fri, Aug 20, 2021, 12:56 PM UTC

quickthrower2 wrote: post #116

ocdtrekkie wrote: post #55

Earlier quoted context omitted.

.NET MAUI seems promising unless you're a VB developer.

Why not just learn C#? Same framework, tooling, target, libraries etc, just a different syntax.

I know C#, and I've worked in it. I prefer VB. (To be specific, beyond language differences, VB's app platform is inherently faster to work in, a lot of it is just built-in that take a lot of scaffolding to replicate in C#. You'd be surprised how much of VB isn't directly available to C# developers.)

Re: Performance Improvements in .NET 6

#179

Post by ocdtrekkie » Fri, Aug 20, 2021, 12:57 PM UTC

tonyedgecombe wrote: post #93

ocdtrekkie wrote: post #55

Earlier quoted context omitted.

.NET MAUI seems promising unless you're a VB developer.

The writing has been on the wall for VB.Net for a long time now.

Only due to mismanagement and apathy by Microsoft. It could and should be as popular as Python is today.

Re: Performance Improvements in .NET 6

#180

Post by apercu » Fri, Aug 20, 2021, 1:02 PM UTC

smackeyacky wrote: post #94

I'm going to pile in too late and sing the virtues of .NET core or whatever its called now. Deployment of web apps to containers is a breeze, the language is modern feeling. Roslyn is about the most awesome thing I have played with. Razor pages are a breeze compared to the giant piles of dependency hell that client side SPAs or node have become. It feels lean and mean and I can be sitting at a debian box or a windows…

I've been in and around platform development in the .NET space for over a decade (not as a developer, I stopped programming for the web in like 2002 because I couldn't stand the the entire front end paradigm).

My biggest issue with .NET has always been how slow it is compared to .

Is there hope?

lol