Linked by Thom Holwerda on Sun 12th Jul 2009 21:29 UTC
Even though news has been slow the entire week due to the fact that it's summer and people are more interested in vacation than in technology news, we still had a lot of interesting stuff this week. Google obviously captured the headlines with its Chrome OS, but we also talked about Mono, Richard Stallman, and many other things.
Permalink for comment 373139
To read all comments associated with this story, please click here.
C# vs Java is not just one language against the other it is also the std libraries of .NET vs JDK and CLR against JVM and the concepts that follow from this.
The .NET libraries are many, many, many times easier to use compared to the JDK libraries. In .NET you have one or two ways of doing a specific thing and you are almost never in doubt what the designers were thinking when they created the API for the given namespace.
You can't be serious. The JDK library is showing its age at some points, but it is fundamentally well-designed. For example, the available collections are reasonably named and also complete. Interfaces are named after concepts, and implementations are named after specific algorithms. For example, you have a Set interface, implemented by a HashSet and TreeSet class.
In .NET there are no interfaces at all for some concepts (for example Set). collection classes are named confusingly (List is an ArrayList, SortedList is not a list at all, but a dictionary where the keys are sorted, etc. ). Thread-safe collections are extremely incomplete.
And don't get me started about the documentation. The MSDN documentation is a complete mess. There are examples in all .net languages, but never more than one paragraph about one topic. For example you have different pages for "type X", "members of type X", etc so you never have a useful amount of information on one page.
Member since:
2006-03-01
C# vs Java is not just one language against the other it is also the std libraries of .NET vs JDK and CLR against JVM and the concepts that follow from this.
The .NET libraries are many, many, many times easier to use compared to the JDK libraries. In .NET you have one or two ways of doing a specific thing and you are almost never in doubt what the designers were thinking when they created the API for the given namespace.
You can't be serious. The JDK library is showing its age at some points, but it is fundamentally well-designed. For example, the available collections are reasonably named and also complete. Interfaces are named after concepts, and implementations are named after specific algorithms. For example, you have a Set interface, implemented by a HashSet and TreeSet class.
In .NET there are no interfaces at all for some concepts (for example Set). collection classes are named confusingly (List is an ArrayList, SortedList is not a list at all, but a dictionary where the keys are sorted, etc. ). Thread-safe collections are extremely incomplete.
And don't get me started about the documentation. The MSDN documentation is a complete mess. There are examples in all .net languages, but never more than one paragraph about one topic. For example you have different pages for "type X", "members of type X", etc so you never have a useful amount of information on one page.