React: Write a function that generates a piece of HTML. Use standard event handlers to manage user interactions. Update state via setState methods. Ship it.
The method for passing data to a dialog component is to import a magic constant and inject a data field into it's constructor? It's a completely over-engineered, nonsensical solution for a problem that doesn't even exist in React. There's so much stuff you have to be familiar with in Angular just to build the simplest features.
Take a look at what you have to go through if you want to create a custom component in angular material (that can sit inside a form):
https://material.angular.io/guide/creating-a-custom-form-fie...
Something has gone completely wrong here.
I can only guess that "same team" was a design-centric subteam for Angular while the engineering-centric team worked on the framework/documentation itself, or that Angular Material was under pressure to get implemented before all the best practices were established and by then they were stuck with the API.
And every release .NET just keeps moving closer to the dumb systems. Simple and raw is good, keep the magic away
The amount of complexity is mind boggling.
I mean, look at Flask in Python. Or even Expressjs in Node, why can't Microsoft come up with a simple framework that can run well on the .NET runtime?
I am a huge fan of C#, having used it for Desktop app development.
I would love to have a framework like flask in the .NET ecosystem.
I found it very simple and minimal (again, other than the DI) when learning it.
Flask is self-described as a "micro framework", which makes it simple to start with, but IMHO difficult to grow into something bigger.
I like the balance the ASP.NET Core 3.0 strikes.
dotnet new webapp -o HelloWorldAnd all of this is easy to customize and change.
"Web API" projects are even simpler-- it's just a small handful of files.
Honestly I'd rather develop in vanilla NodeJS where the approach is at least consistent, than in the Express ecosystem where sure your problems may have been solved 1000 different ways already but where none of them really fit what you want to do, and where there are many layers of hidden incompatibility that are going to require you to make adapters for each library anyway.
I am judging from my experience developing applications with 200+ developers across continents. You can write crappy code in Angular as well, but it helps you govern your architecture and your app. If you want modular components that can be reused, go for Angular. For smaller things or landing pages use Vue, React.
My experience.