3 ms·
The most sane option, really? You'll use a runtime without garbage collection. And a GUI framework, vastly inferior to say WPF ( GUI accelerated, XAML DSL, tool
by borisk 16y ago
The most sane option, really? You'll use a runtime without garbage collection. And a GUI framework, vastly inferior to say WPF ( GUI accelerated, XAML DSL, tools for designers ).
- strlen 16y agoI said "sane" not elegant or beautiful or "best in every occasion". I'm also speaking in terms of cross platform. .NET is an excellent platform for Windows development and I won't dispute that. I am very well aware of Mono, but it still involves tying myself to a Microsoft standard (plus it's always going to be behind in terms of both language and libraries). As I've mentioned earlier, I am fine without garbage collection for desktop applications (implementing complex parallel algorithms is a different matter -- there GC very clearly helps). Sure GC is very nice to have even when you can make do with manually finding/fixing leaks (I'd rather focus on something else), there are many other advantages to high-level languages than just garbage collection (actual RTTI/reflection -- not very possible in C++, richer built in collections, callbacks without function pointers or "operator ()"; in the case of Scala, F#, Lisps -- and to a lesser degree C# -- there is functional programming, closures, DSLs, etc...)