News for hackers. Stuff that matters.

A comment on Programming the Commodore 64 with .NET. Parent comment

Re:Programming the Commodore 64 with .NET by briHass on Wednesday November 19, 2025 @12:45PM (#45982423)
Honestly, .NET should be the default choice for any non-trivial backend or non-GUI application. I assume the legacy (outdated/inaccurate) perception of MSFT's stewardship is the only reason anyone reaches for something else.

AOT is a game changer for native binaries, but even with fw dependence, the cross platform support is excellent (we deploy to Linux servers frequently.)

[ Parent | on HN ]
Re:Programming the Commodore 64 with .NET by osigurdson on Wednesday November 19, 2025 @03:20PM (#45984597)
>> .NET should be the default choice for any non-trivial backend or non-GUI application

I personally wouldn't go that far. If you know well, it makes sense to use it, but you already know Java or Go, would the benefit delta isn't going to be that high.

Somewhat famously, even Anders Hejlsberg decided to use Go vs .NET for the new Typescript compiler. .NET is fine (and I have personally used it a lot) but that doesn't mean it is net better than other options out there.

[ Parent | on HN ]
Re:Programming the Commodore 64 with .NET by ivm on Thursday November 20, 2025 @02:34PM (#45996672)
For GUI there are Avalonia (cross-platform WPF), Uno Platform (cross-platform WinUI) and old-school bindings to native UI frameworks on Android, iOS & Mac (you can do UIKit/AppKit in C#), and of course Windows.
[ Parent | on HN ]