est. 2018 · szczecin, poland ● availability: open — 1 retainer + 1 short build vol. viii — no. 42 · may 2026
late edition
EN·PL·
„Moin." Mein Deutsch reicht gerade fürs Essenbestellen, „die Karte, bitte" und „zahlen, bitte". Für alles Weitere — lieber Englisch oder Polnisch. 🍺

The Perliński Gazette

all the stack that's fit to ship
single issue
one email
§ a4 — notes from the workshopTechnology2026.01.09
← all dispatches

Picking .NET in 2026 (on purpose)


Every couple of years someone declares .NET dead, and every couple of years it quietly ships another release that's faster than the last. In 2026 I still reach for C# on enterprise-shaped problems, and not out of nostalgia.

Boring is a feature

The clients who pick .NET are picking a decade of LTS releases, a debugger that works, and a hiring pool that doesn't evaporate when a framework falls out of fashion. "Boring" here means I can still run this in five years — which for a b2b system is the entire point.

Where it genuinely wins

  • Throughput per watt. Modern .NET is shockingly fast, and the AOT story keeps improving.
  • Tooling. Roslyn analyzers catch whole categories of bug before they reach review.
  • Azure-shaped deployments. When the rest of the org already lives there, fighting it is a tax you pay forever.

I write plenty of Python — it's my day-to-day. But when a client says "this has to still be here, and still be supportable, in 2031," I'm reaching for C# and not apologising for it.