Hmm. I find that most documentation is wretched, but the .NET documentation doesn't seem to suck any more than any other. The biggest lack I've seen in the MS documentation are comprehensive, working examples. Many of the .NET code snippets are trivial and do not show the background work you need to do.
Hmm2. How so? Even though I'm stuck using .NET 3.5, I've generally found that implementation to be stable.
obscene learning curve
C# the language was easy to learn, starting from a C/C++ background. The most surprising thing about C# and .NET was learning to not reinvent the wheel. Time after time I would start implementing some sort of plumbing, only to discover there was a .NET class for it.
Probably not on the list because of the number of other surveys saying Swift has largely overtaken ObjC.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
But still Java/Kotlin are at the moment a "pair" (for Android) compareable to ObjC/Swift for iOS. And Kotlin is there, but ObjC is not.
While Swift nowadays has more devs than ObjC (totally understandable when I think about the cruel strange syntax of ObjC... a miracle how this language could be successful EVER), Kotlin still looks for ppl to adopt it.
I personally do like Kotlin very much but still, the support in Android Studio has its flaws... It's not a "first grade citizen" as it has been promised.
Every project still gets the Java Folder structure and no Kotlin folders by default... You always feel like a foreigner when u start to code Kotlin in an Android project.