5 ms·
I've honestly given up. The new "open" development style of .NET Core is not my cup of tea. It's now riddled with MVP features that are 80% complete, bug-ridden
by jiggawatts 6y ago
I've honestly given up. The new "open" development style of .NET Core is not my cup of tea. It's now riddled with MVP features that are 80% complete, bug-ridden, and undocumented other than couple of blog articles.
The compatibility break with the .NET Framework also removed the biggest advantage I saw in C#, which was that any code that I wrote would "just work". Now there's more frameworks, standards, cores, and build flags than I care to learn, and there are all too many scenarios where it's flat impossible to do something that was trivial before.
This is the reason, for example, that PowerShell Core is past version 7 but is still missing many modules, including some key Microsoft ones. If they can't figure this out, what chance do I have? Why would I bother?
Lastly, I got fed up with Microsoft releasing yet another half-baked GUI framework. What's the latest one? MAUI? It's yet another attempt at having one framework to rule them all, which means that it'll inevitably be the lowest common denominator and not good at anything. Microsoft won't actually bother making it good enough to write a flagship application in it, and they won't write any of their own apps with it. It'll be dropped on the floor and replaced by the next incomplete GUI framework within just a few years, mark my words. That's if it's ever finished!
- mariusmg 6y ago>The new "open" development style of .NET Core is not my cup of tea. It's now riddled with MVP features that are 80% complete, bug-ridden, and undocumented other than couple of blog articles. .NET Framework is a product, .NET Core is a OSS project. When .NET 5 will ship it will be even worse since .NET Framework people will just expect things to work.
- tonyedgecombe 6y agoI suspect a lot of people (myself included) will just stop at 4.8.
- jiggawatts 6y agoJust this week I wanted to spin up a minimalist ASP.NET page for "tyre-kicking" of new infra builds. You know, something that just coughs up a single page with some basic info, such as the regional options, time zone, current time, and the latency to the SQL Server. This checks that the infra guys did their job and that the AD accounts and firewall ports are in place. I wanted to write 1 page with just some dynamic labels, that's it. Nothing fancy. No MVC. No dependency injection. No JavaScript frameworks. No CSS. Just one ASPX or CSHTML page. Visual Studio 2019 no longer ships with a web project template that does that. Every single project type coughs up megabytes of crap and a bunch of scaffolding. After hours of clicking through every project type, I resorted to another hour of googling to discover that the "legacy" empty templates are still there, but only available as a hidden install option! It's madness.
- mariusmg 6y ago>No dependency injection. No JavaScript frameworks. >Visual Studio 2019 no longer ships with a web project template that does that. Every single project type coughs up megabytes of crap and a bunch of scaffolding. Yeah, the way depency injection and multiple JS frameworks are shoved down your throat in .NET Core is sooo annoying.
- GordonS 6y ago> Yeah, the way depency injection and multiple JS frameworks are shoved down your throat in .NET Core is sooo annoying I've been using dotnet core for years and precisely zero times I have had any JS framework shoved down my throat.
- JamesNK 6y agoIt is strange that you couldn't find the empty web template. Every version of ASP.NET Core has come with one. Empty is the first option in the "Create a new ASP.NET Core web application" dialog in VS2019, and "dotnet new web" creates an empty website via the command line. What did you need to do to create an empty website? Disclaimer: I work on ASP.NET Core
- jiggawatts 6y agoThe most minimalist ASP.NET Core template I could find made it too difficult to create a "page" with some code-behind. I could create a CSHTML page and inline expressions worked, but I couldn't convince it to execute anything from a matching cs class. I did google this, and it's not like I hadn't written Razor syntax pages before, but that was a few years ago and my memory was fuzzy. What I found was that Razor pages are now part of any number of very similar sounding but wildly different frameworks, and code samples for one do literally nothing in the other. It's not even self-evident which framework I'm "in" for any given project. Half of it seems to be just convention, the other half is explicit configuration, and it's all version specific. I tried to go back to classic ASP.NET, thinking that that's actually a better fit for the type of legacy web app server testing that I need to do. That's where I found the new project templates that pull in more code by default into an "empty" project than I've written in the past half a decade.
- SideburnsOfDoom 6y ago> It's now riddled with MVP features that are 80% complete, bug-ridden, and undocumented other than couple of blog articles I work full time with ASP .NET Core 3.1 projects, and I don't recognise this at all. I don't think that it's correct.
- snak 6y agoSame here. Generic hateful statement from a developer that probably has spent a couple of days at most in .NET.
- GordonS 6y agoSame here, this is just utter nonsense. I have to assume the person that wrote that comment hadn't actually been using dotnet Core at all. I note how they provide no examples of bugs from this "bug-ridden" and "undocumented" platform. I've been using dotnet since it was originally created many moons ago, and dotnet core is the best incarnation yet. Documentation is excellent - I don't think I've ever once came across an undocumented feature?!
- SideburnsOfDoom 6y ago> dotnet core is the best incarnation yet. To be fair, we didn't use .NET Core extensively before .NET Core 2.1, because it was not quite ready yet. But since 2.1, we haven't looked back.
- pjmlp 6y agoMAUI is Xamarin rebranded. Even with its half broken implementations, .NET and Java are still the best options in tooling and managed runtime capabilities.
- jiggawatts 6y agoIf it was just marketing name change, it would be available now. Their current timeline has the first production release in late 2021!
- pjmlp 6y agoIt cannot be available now, because Xamarin doesn't support all backends that MAUI should support, nor does it run properly on .NET 5 yet.
- tasogare 6y agoAnd it will be crap. What I want, and I'm sure a lot of other devs interested in making C# GUI multi-platform apps, is an UI framework à la Flutter that display the same thing everywhere. In the days of Electron apps not having a native look and feel is not a really problem anymore. The saddest thing is that Microsoft actually offered that years before: Silverlight Out-of-Browser applications, that where running the same on Windows and Mac OS.
- nbevans 6y agoThere are rumours of a Flutter back-end coming for Xamarin.Forms/MAUI. Or possibly a something lower level in Windows itself (which a MAUI back-end could tap into).
- pjmlp 6y agoElectron is just a phase like Active Desktop and XUL, its time is coming to pass in this fashion driven industry. Flutter is Dart Rails, the last hope to save Dart.
- rubber_duck 6y agoSilverlight was good for it's time but nowadays I would rather code in whatever popular JS/HTML framework - the live reload beats any C# flow hands down in iteration time and the fact that I can just reverse proxy my local dev env while working on something to a designer speeds up design tweaks a bunch.
- josteink 6y ago> The compatibility break with the .NET Framework also removed the biggest advantage I saw in C# I'll be honest here. The migration from .NET Framework to .NET Core is a pain. I see why things were done the way they were done, but it's still a real pain. That said: for green-field works NET Core is clearly superior. > PowerShell Core is past version 7 but is still missing many modules, including some key Microsoft ones Just like .NET Core's main mission was not to replace the entire .NET Framework, the same applies to PowerShell Core. .NET Core was created to make developing .NET-based web/cloud-services easier, faster, using less space/resources at runtime, and to have a fully supported cross-platform story. And at that it has been a wild success. Almost everything about .NET Core is better to work with than the traditional .NET Framework (at least for the workloads it was intended for), and I'm always depressed when I have to move back to work on the "old" stack. In this regard PowerShell Core is (as I see it) not meant to fully replace regular PowerShell either, but to be a good platform to do your cross-platform dev-ops'y build and deployment scripts related to your .NET Core deliverables. It may not be what you want it to be, but it has a clear mission, and it's delivering fairly well on that. > Lastly, I got fed up with Microsoft releasing yet another half-baked GUI framework. I think this applies to pretty much everyone, which is why they never catch on, and Microsoft inevitably trying to "solve" this by releasing yet another framework. That said the MAUI-presentation on this year's Build looked pretty convincing. If I had time to spare and had some small projects/POCs I had to work on, I might had given it a spin.
- ptx 6y agoBut if .NET Core was not meant to replace the .NET Framework, why is Microsoft doing just that with .NET 5? (Yes, the old framework will still exist after it's been replaced - the same way VB 6 still exists after being replaced by VB.NET and IE still exists after being replaced by Edge.)
- josteink 6y agoYou are allowed to change your mind, aren't you? :) The goal for the initial .NET Core project was to have something cross-platform, modular and lightweight to build Linux-deployable cloud-services with. Once that reached a mature state, they could expand scope. And now, after .NET Core 3.x has landed, it has matured so much, that MS can see one single unified path forward which also includes some things which previously was only possible using the traditional .NET Framework (4.8). So now they are adding those use-cases to the "Core" package as well, without compromising on what .NET Core was supposed to deliver. I honestly don't see anything wrong with that.
- jfkebwjsbx 6y agoThe problem is not the "open" development. The actual issue is this new Microsoft full of half-done projects and trying to reduce engineering costs. They even try to make others write the documentation for their products... MSDN is gone and now docs are a mess. Ballmer was a mess, but at least he got the devs-first bit right. Nowadays it is devs-last, cloud-first.
- pjmlp 6y agoHere I have to sadly agree, but I think the cause is something else. Lots of new blood full with ideas to leave their mark.
- ourmandave 6y agoIs MAUI the death knell for Project Reunion?
- pjmlp 6y agoMAUI on Windows is based on WinUI, so no. Those projects are orthogonal.