.NET 10 Preview 6 brings JIT improvements, one-shot tool execution

Post by cheschire » Thu, Jul 31, 2025, 12:24 AM UTC

sumtechguy wrote: post #93

qingcharles wrote: post #56

Earlier quoted context omitted.

This thing has barely changed in the ~30 years I've been using it. There's definitely room for some more improvements.

You can divide visual studio into 4 era's. The vs6 (we smashed all of our dev tooling together and its integrated decently) era, the vs2002/vs2003/vs2005 (we broke it all and you will like it and never speak of C++ again), vs2010 era (we fixed all of that from 2002 sorry about that), vs2017/vs2022 (it updates from the internet and takes forever to install and now does everything). The problem is MS is unwilling to st…

Post by brokencode » Thu, Jul 31, 2025, 12:32 AM UTC

cheschire wrote: post #171

smackeyacky wrote: post #142

All these changes, yet still no satisfactory UI framework. Still no migration path from WinForms to something modern. I love .NET but if you're taking on an older desktop app that is still using VB.NET and WinForms it feels like Microsoft have decided to let you circle the drain with no supported way forward into MAUI or whatever stupid XAML UI they decided is the solution these days. On a server, .NET is fantastic a…

I've tried each iteration of UI paradigm they've tried since WinRT and never really had any significant problems with any of them. WinRT, UWP, WinUI, MAUI... But then they aren't even willing to invest the time to dogfood their own products and fully replace the windows UI. Really doesn't inspire confidence. I suspect they also made a bad bet by going so hard on blazor without putting more support behind WASM itself.…

Post by reactordev » Thu, Jul 31, 2025, 12:47 AM UTC

pjmlp wrote: post #146

reactordev wrote: post #73

Earlier quoted context omitted.

The issue was in the beginning they didn’t think interop with C/C++ was value add. People complained and they added “Managed C++” which unfortunately influenced C++03’s design a lot. It wasn’t until C++11 that Microsoft gave up. You couldn’t effectively interop with C++ without writing a managed C++ wrapper, which only worked on windows. They added support for P/Invoke to aid in Win32 calls (shell.dll, user32.dll) as…

You are jumping over a few facts there. P/Invoke was born as J/Direct on J++, it became P/Invoke after the lawsuit, and Cool project turned into C#. Managed C++ Extensions in .NET 1.0 got replaced by C++/CLI on .NET 2.0, it was a .NET Core 3.1 milestone to support it, and has recently been updated up to C++20, minus modules. Still heavily used among .NET community on Windows. Meanwhile the native C++/CX and C++/WinRT…

Post by athrun » Thu, Jul 31, 2025, 12:59 AM UTC

pshirshov wrote: post #158

nickpeterson wrote: post #133

Earlier quoted context omitted.

I agree, but somewhat paradoxically, F#’s lack of new features kind of becomes a feature. Have you seen the number of C# features added in the last 5-10 years? It’s crazy

Half-baked adhoc features which didn't bring the language closer to Scala. Still no HKTs and typeclasses, call-site expansion can only be simulated with partials and text-level code generation, etc, etc.

Post by adabyron » Thu, Jul 31, 2025, 2:20 AM UTC

thewebguyd wrote: post #51

pjmlp wrote: post #16

Earlier quoted context omitted.

I very much doubt about TS.Net, given the rewrite in Go decision. .NET nowadays has a serious adoption problem, and they should spend more time talking with their own colleagues at Azure, about their use of Java, Go, Rust.

> .NET nowadays has a serious adoption problem It's seriously going to make people question the future of the platform. Look at Microsoft's actions, not their words. TS Compiler: Go New TUI Editor: Rust Winget: C++ (this would have been a great candidate for .NET) At least PowerToys is C#. .NET is great, but why isn't it good enough for Microsoft? The company that historically has had such a strong culture of dogfood…