3 ms·
While competition can be good sometimes, I am not convinced it's a good thing when it comes to GUIs. See Linux desktop fragmentation. In the .NET community we
by DeathArrow 2y ago
While competition can be good sometimes, I am not convinced it's a good thing when it comes to GUIs. See Linux desktop fragmentation.
In the .NET community we have the ideea that should be one tool for one job, one library, one framework etc. Now for Gui we have Avalonia, Uno and MAUI which can lead to fragmentation, noise and clutter and can reduce code reusing.
It would be nice if most people will pick one tool and stick to that.
- moron4hire 2y ago> In the .NET community we have the ideea that should be one tool for one job, one library, one framework etc. I've been a .NET developer for 20 years. This is not true.
- ethbr1 2y agoWhat about WinForms? Afaik, that's been the only Windows GUI framework wth long term support. /s
- DeathArrow 2y agoMost people used EF for ORM, Newtonsoft for JSON, Automapper for object mapping built-in DI container for dependency injection, XUnit for tests, Fluent Validation for validation, ASP.NET WebApi for web applications, ASP.NET MVC for websites and so on.
- taspeotis 2y ago> In the .NET community we have the ideea that should be one tool for one job, one library, one framework etc. xUnit, NUnit, MSTest Autofac, Ninject, Microsoft.Extensions.DI Quartz, Hangfire
- DeathArrow 2y agoYes, there are multiple tools but for each task there is a dominant tool. That is my impression.
- high_priest 2y agoA "dominant tool" is the one Visual Studio sets default for installed workflow package
- swalsh 2y agoYeah, there are some categories with choices, but 9/10 use cases the .net ecosystem is Trader Joes.
- sasakrsmanovic2 2y agoCompetition is always good, especially when healthy and productive. See any industry, why would software be any different. Especially when there is also collaboration. Uno team collaborates quite a bit with .NET, Visual Studio and MAUI teams.