LINQPad – The .NET Programmer's Playground

Original Article ↗ Hacker News Discussion ↗

Overall sentiment and use cases

  • Widely described as a “must‑have” / “essential” mini‑IDE for .NET.
  • Common uses:
    • Rapid prototyping, scratchpad code, and small utilities.
    • Ad‑hoc data access and transformations, including multi‑database queries.
    • Exploring libraries/BCL behavior, new C#/.NET features, and debugging tricky cases.
    • Acting as a personal “CMS” for scripts, sometimes distributed via NuGet or run with lprun and cron.
  • The Dump visualizer and drill‑down output, integrated debugger, SQL translation view, Benchmark.NET integration, and IL decompilation are repeatedly cited as major productivity boosts.
  • Many prefer it to Visual Studio’s C# Interactive or spinning up a full console project for small experiments.

Alternatives and complements

  • Mentioned alternatives: RoslynPad, CSharpRepl, NetPad, dotnet-script, Jupyter/Polyglot notebooks, dotnetfiddle/ideone, VS Code + extensions, JetBrains Rider.
  • NetPad and RoslynPad are praised as free/open options, though less polished and sometimes missing features (e.g., syntax tree tooling in some cases).
  • Several people still end up using plain console apps, Jupyter, or web-based fiddles for cross-language or lighter-weight use.

Licensing and updates

  • Licenses are perpetual per major version; major versions come roughly every two years and track .NET LTS.
  • Some users are happy to pay and have repeatedly upgraded; others dislike needing to buy upgrades tied to new .NET versions and have switched away.

Platform support and cross‑platform debate

  • A major criticism is that LINQPad is Windows-only; some see this as a blocker or even as marking it as a “toy.”
  • Others argue the core audience (C#/.NET developers, especially on Windows/SQL Server) makes this acceptable and that supporting Linux/macOS is costly.
  • There is active work toward macOS support via Avalonia XPF; timeline is unclear.
  • NetPad and web tools partially fill the gap for non‑Windows users.

C#/.NET ecosystem and tooling discussion

  • Extended side debate on whether Microsoft is “serious” about C#, its role on Azure, and desktop vs web focus.
  • Mixed views on non‑Windows .NET tooling: some report good experiences with Rider and VS Code; others highlight missing features (e.g., certain debugger autocomplete and syntax tree visualizers) and high dependency on third‑party tools.