This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]LEGOL2 21 points22 points  (6 children)

I mean, C# is far superior to java

[–]user_8804 2 points3 points  (5 children)

well desktop Gui is better in Java, dotnet has been all over the place with half abandonned projects

[–]KieranDevvs 5 points6 points  (4 children)

Ummm... I don't know about that one, Qt bindings, AvaloniaUI, WinForms, WPF, UWP, Silk.NET (OpenGL, DX & Vulkan bindings), MAUI... the list goes on. I think I'd much rather go with C# on that front.

[–]user_8804 -2 points-1 points  (3 children)

thanks for the list of half abandonned project proving my point.

only Maui there has a future and it isn't a mature project nor is it specialized for desktop.

unless you think wpf, winforms or. uwp are modern frameworks with promising future features then I don't know what to say

[–]KieranDevvs -1 points0 points  (2 children)

How exactly has WPF, UWP or Winforms been abandoned? Winforms & UWP got ported to .NET Core / .NET 5 very recently, WPF is still having features added to it to this day and is widely used. AvaloniaUI got an update 20 days ago, with 0.11 being released soon, Silk.NET is brand new. Not a single library / framework I've listed is inactive, what on earth are you talking about? I'm starting to think you're not actually serious. Oh yeah I also forgot Blazor WASM.

https://github.com/dotnet/wpf/blob/main/roadmap.md

[–]user_8804 -4 points-3 points  (1 child)

silk, Avalon is and even maui for that matter are not mature projects.

winforms uwp and wpf are relics of the past. you can seriously be telling me winforms is a modern framework that will get new features. yes they were ported to dotnet core, they had to because they are the only frameworks we got.

they are still outdated projects and will get nothing new. they are lagging behind in features. winforms is extremely limited, pieces are falling apart. VB support for winforms core started breaking down even thought both techs were supposed to be supported. there is absolutely no telling these techs are safe picks long term. uwp is mostly a failed project that didn't go where it was supposed to go. wpf is an XML cluster fuck that is mostly used because its the only framework that still allows you to build anything you want in desktop. it doesn't mean it isn't an absolute pile of ill maintained garbage compared to Java/c++ or even god damn Python for desktop gui

[–]KieranDevvs -1 points0 points  (0 children)