Someone other than Oracle maybe pleased with the lawsuit:
Too many engineering resources are devoted to Android at Google and at their partner companies, but I can not help to think that Google could migrate Android from Java to the ECMA/ISO CIL and C#.
Google could settle current damages with Oracle, and switch to the better designed, more pleasant to use, and more open .NET platform.
Working with not so good developers is not fun: How I Feel About The .NET World Lately.
The higher-end developers generally try to share their knowledge and experience with others, but in doing so, will waste a lot of time and effort going against the backlash they’ll get from the lower-end developers. The lower-end developers frequently accuse the higher-end developers for making things more complicated than they need to be, while they fail to realize that their initially simple solutions (as recommended by Microsoft of course) only leads to severe complications later on.
I don’t think this is dot net specific. You can feel the same in Java-land when your project is weakly staffed.
Nice line:
The low quality of the guidance and the tools is the reason why i have started referring to the typical Microsoft recommended development practices and products as Fisher Price Development.
In Why Scala’s “Option” and Haskell’s “Maybe” types won’t save you from null Cédric Beust tries to get his head around the Option type. The actual discussion is in the comments of Tony Morris, Daniel Spiewak and James Iry.
A nice summary of common Maven pain points and some marketing for Gradle from the Hibernate community: Steve Ebersole - Gradle: why?