Performance Improvements in .NET 6 • Hacker News Board

Re: Performance Improvements in .NET 6

#251

Post by whoknowswhat11 » Sat, Aug 21, 2021, 3:03 PM UTC

lbriner wrote: post #153

EMM_386 wrote: post #96

Earlier quoted context omitted.

> Did they just lose their minds there? Hire a bunch of idiots caught up in fads instead of folks who've been around for a bit. No, they just took the focus off the Windows UI. They went cross-platform with .Net Core, which enables it to run in the cloud on Linux boxes. This was the focus. I hope they come back around to a proper .Net WinForms designer under .Net Core, but for now the full framework can be run and wi…

It is funny how much they have strived for one platform to rule them all when it would have been easier and cheaper just to maintain windows, web and mobile separately and kept the frameworks suited to their particular platform.

I actually think they could have gotten winforms x-platform by now if they'd tried. Or some kind of x-platform story if they wanted.

The endless other crap has just eaten dev time like crazy.

Re: Performance Improvements in .NET 6

#252

Post by tomnipotent » Sat, Aug 21, 2021, 4:56 PM UTC

jcelerier wrote: post #168

R0b0t1 wrote: post #157

Earlier quoted context omitted.

C++ builds are only bad when you use too many templates, which Chrome famously does. If you use MSVC you get some additional speedup as well because it tries to avoid disk IO. I would say Qt on Windows is probably a worse idea than just using .NET as it ties into the OS. If you need cross platform and normally use Windows it's not a bad idea.

> C++ builds are only bad when you use too many templates, if that was the case I would see the same build times when building the exact same project with the exact same compiler on Linux versus on Windows. Yet Linux is really much faster.

Disable Windows Defender before your next build.

Re: Performance Improvements in .NET 6

#253

Post by oaiey » Sat, Aug 21, 2021, 5:37 PM UTC

pjmlp wrote: post #226

ripley12 wrote: post #198

Earlier quoted context omitted.

That’s on the Windows team, not the .NET team.

Except .NET and Windows belong to same package and some APIs are only available in .NET as COM wrappers.

The languages are all owned by Scott Hunter. Including e.g their Java support etc. The windows sdk not. Where exactly the language projections are, no idea. IDL and COM however sounds indeed more like Windows team and not language and runtimes team.

Re: Performance Improvements in .NET 6

#254

Post by pjmlp » Sat, Aug 21, 2021, 5:59 PM UTC

oaiey wrote: post #253

pjmlp wrote: post #226

Earlier quoted context omitted.

Except .NET and Windows belong to same package and some APIs are only available in .NET as COM wrappers.

The languages are all owned by Scott Hunter. Including e.g their Java support etc. The windows sdk not. Where exactly the language projections are, no idea. IDL and COM however sounds indeed more like Windows team and not language and runtimes team.

Yeah, classical Microsoft where externals have easier time talking across divisions than internal employees, only interested on their own silos.

I know of cases where externals where tasked with fetching information due to that culture.

Re: Performance Improvements in .NET 6

#255

Post by de_keyboard » Mon, Aug 23, 2021, 7:07 AM UTC

rspeele wrote: post #236

de_keyboard wrote: post #151

Earlier quoted context omitted.

C# is more popular but actually harder to learn IMO (although this does depend on your prior experience). C# is huge, but F# achieves more with fewer language constructs. F# can also be transpiled to JavaScript, which is a huge advantage.

I love F#, it's my #1 favorite language by far. But I code in C# at my day job and I gotta say, while I haven't exactly kept count, it's hard for me to agree that F# has fewer constructs. To be fair, much of that comes from the fact that F# has to do nearly everything C# does for compatibility, and have its own stuff too. It leads to a lot of "wait, which tool do I use for this problem?" questions for newbies. * [ ]…

This is a fair point! Although I was more talking about the language constructs that are used for 90%+ of code, which from my own experience is:

  * let
  * discriminated unions
  * records
  * lists
  * seq
  * async
  * fun

Like all languages people actually use, F# has a long tail of advanced features!

Re: Performance Improvements in .NET 6

#256

Post by Const-me » Wed, Aug 25, 2021, 2:10 PM UTC

vips7L wrote: post #201

DonnyV wrote: post #199

Earlier quoted context omitted.

Microsoft should either use Flutter or make a C# version of something like Flutter. Its simple to understand and doesn't have any magic xaml tag to make things work.

Isn't this just .NET MAUI?

Flutter is somewhat similar to UWP, it includes a cross-platform rendering engine.

MAUI is similar to old Xamarin, it exposes whatever native controls are available on the platform.

Useless for me because I sometimes develop GUI for embedded platforms which don’t have any native controls at all.

Even ignoring the embedded use case, I believe that’s not the right approach overall. Native controls are too different across platforms. Commercial success of Electron demonstrates people don’t give a crap about native controls, they want good UX identical across the platforms, in large part because it saves development costs for cross-platform stuff.