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

Original Article ↗ Hacker News Discussion ↗

Blazor, Hot Reload, and Tooling Frustrations

  • Several commenters say server-side Blazor is conceptually great (type-safety, ORM, performance) but hampered by unreliable tooling:
    • dotnet watch/Hot Reload often misses CSS or component changes, especially in Blazor and MAUI hybrid projects.
    • Razor/Blazor editor experience (syntax highlighting, IntelliSense) is described as flaky even in current Visual Studio, with some comparing it unfavorably to XAML/WinForms “code-behind” approaches.
  • Others report Hot Reload works “mostly fine” when run from the terminal or in full Visual Studio, but still breaks too often for comfort in some IDEs (e.g., Rider on macOS).

Blazor vs HTMX / Web Approaches

  • Discussion compares Blazor (server, static SSR, WASM) to Razor Pages + HTMX:
    • Static server-side Blazor plus selective interactivity is praised as fast and simple, similar to Razor Pages.
    • Some see websocket-based Blazor Server as overcomplicated, reminiscent of old ASP “runat” confusion.
    • Blazor WASM is considered viable mainly where shipping the .NET runtime to the client is acceptable (enterprise/SPAs, code sharing); for many apps, HTMX + Razor is viewed as “KISS” and sufficient.
  • Several wish components existed directly in MVC/Razor Pages so Blazor could be de-emphasized.

Ecosystem, Adoption, and Open Source

  • Many praise .NET as a “sane” ecosystem: strong CLI, packages, debugging, cross‑platform CoreCLR, and continual perf improvements (Span, AOT, etc.).
  • Others argue .NET has an adoption problem, noting high‑profile internal Microsoft projects choosing Go/Rust/C++ instead, and long‑term confusion around Framework/Core/Standard/Mono.
  • Debate on third‑party ecosystem: some feel Microsoft “blesses” a single stack and crowds out alternatives; others list numerous sizeable OSS .NET projects and see NuGet as healthy.
  • One commenter warns about compiler IP; multiple replies stress Roslyn and runtime are MIT-licensed.

CLI, Formatting, and Scripting Improvements

  • New one-shot tooling (dotnet tool exec) and dotnet run app.cs scripting are widely welcomed, compared to npx.
  • C# scripting is seen as a strong alternative to PowerShell for larger scripts, especially with top-level statements and NuGet references, though docs are currently confusing.
  • For formatting, opinions split:
    • dotnet format is official but seen as slow and not fully deterministic.
    • csharpier is praised as the “Prettier for C#”, good enough for CI enforcement and widely used by some teams.

Versioning, Upgrades, and Desktop UI

  • Some prefer .NET Framework 4.8 for its “installed everywhere” status and simple XCOPY deployment; others find modern .NET upgrades (post-Core) mostly painless and worth it for performance and language features.
  • Strong dissatisfaction with Microsoft’s desktop UI story: no clear migration path from WinForms, multiple abandoned or overlapping stacks (WPF, UWP, WinUI, MAUI, Blazor), and lack of dogfooding. Avalonia is cited as a saner community alternative.