It's also hard to keep a straight face when someone calls themselves an engineer, but makes absurd claims like "x is more productive" without ever presenting proof or measuring such a quantifiable claim.
I probably also yell at the kids on my lawn.
It's also hard to keep a straight face when someone calls themselves an engineer, but makes absurd claims like "x is more productive" without ever presenting proof or measuring such a quantifiable claim.
I probably also yell at the kids on my lawn.
That's the stupid nature of our industry. Everything is buzzword driven.
There's incredibly good aspects to .NET, and it was better in the past than it is now relative to the competition..
However it's been a victim of it's own success, both in attracted a lot of recent mediocre talent due to it's success, and in growing more complex in it's 15 year lifespan so far. The platform complexity has increased significantly with PCLs, .NET Core, and moving from a dependable 18 month release cycle to a fragmented multi-channel release cycle.. ostensibly to keep up with the competition, but really just getting trapped into a classic prisoners dilemma of a race to the bottom of fragmentation and dependency hell. I think they should have left that particular trick to the Javascript framework of the month ..
Another issue that holds .NET back is licensing, startups don't want to worry about the licensing in case they scale. .NET core is improving this though and there is a huge amount of open source .NET code available.
Despite these drawbacks it's still an awesome platform, with possibly the best general purpose language available in C#. But it's not cool, and yes a lot of that is cargo cult based misunderstanding of it's abilities.
The argument for doing things the current way should be at least as good as the one you'd require to permit a change.
(I am on the backend where things are maybe not so crazy as JS framework world).
I definitely think React is one such example in the front-end world. It fixes so many of the horrible patterns that came before it.
Yet many of it's patterns are rehashing of previous front end patterns - it's very similar to e.g. Winforms in a lot of ways.
Conflating Javascript front end to front end in general is just an example of the myopic short sighted focus of the overall Javascript community, that caused them to miss out on the pre-existing body of knowledge in other languages for as long as it did..