I agree with all you said, but i'm referring to the previous comment where ms has been all but asleep in the last 10 years :D
Anyway talking about language and dev-environment are two completly different conversations, and i'm not wrong saying that Java as language stagnated far too long. I never said the .net eco system thrived meanwhile :D
That's unfortunate, since ms opensource journey started 10 years ago :D
Java as a language stagnated 10 years compared to anything (example lambda).
.net has been the source of many technologies, CQRS/ES, Async/Await, Reactive Programming, etc.
Net core is production ready since more than 1 year, Net Core tooling was not perfect until 6 month ago. Still the whole project from zero to version 1 in 2 year is not fast, its insanely fast ! Find something with comparable features made in less time (runtime, libraries, tooling etc..)
If you program like that i'm sorry, you are doing it wrong. You really just need very few try catch blocks in a standard lob application, a few more if your are using some style of communication that requires it. If your code base is polluted with try blocks i think it's a mistake.
You mistake 2way data binding with ui decomposition and right view model structure, if you have those problems.
With the right view models everything becomes is easy and simple, but you do not get there right away, it's hard to learn, and no framework will bring you there.
This is due to ppl spending way to much time chasing frameworks in vogue, than learn to architect applications.
I love vue btw.
You do not need those specific app, you need to access to those services: I use gmail account in wp mail client or web, here maps owns gmap in any way, google calendar has integrated client like contacts.. Pls do not talk without experience
I agree and i would add that betting on a framework is a huge risk, relying on a library is far less dangerous. In the comparison there are some of both so the example are a bit misleading.
For example to my knowledge knockout is far from stagnating, it does 1 thing only and it does it well, you can easy replace it incrementally in any application.
I agree with all you said, but i'm referring to the previous comment where ms has been all but asleep in the last 10 years :D Anyway talking about language and dev-environment are two completly different conversations, and i'm not wrong saying that Java as language stagnated far too long. I never said the .net eco system thrived meanwhile :D