Frankly speaking, I have never rejected the language of the view, has been to choose the best language for the project, of course, the best is from many aspects, the first consideration is the personnel issue, after all, 28 laws in any language is obvious, any language can meet the daily development of 80%.
However, occasionally will ridicule some strange places, such as today, when the cache is intended to sacrifice the Hashtable, such a powerful thing. NET can not be realized, do not need to do their own, it is true that Microsoft did not want to look, so they write the function code:
Very ordinary very common code, but a careful look, the heart of a sudden kind of want to laugh feeling, press the F12 inside to see it is like this:
This thing is too familiar with, because many years ago just learn Java when used to Hashtable when more curious why the second T is lowercase, this does not conform to the Sun's style ah, the entire JDK is the standard hump, so with this question over a lot of books, see a lot of information, the final conclusion is:
Hashtable's second T-lowercase is Sun's fault, many books mention the problem, many people have suggested to Sun to revise, and then Sun did discuss the problem of T, but because Hashtable is the product of jdk1.0:
Blind substitution will lead to a lot of old system is not compatible at all, so Sun decided to keep the lowercase t, let it continue unreasonable existence, at that time did not care too much, until see C # side of the Hashtable, the heart a little happy flowering feeling, so probably turned a lot of C # class, In fact, like Java, is the standard hump, but Hashtable is very exceptional, but it may be I understand the very superficial, no understanding of the depth of the place.
C # and Java have too many similarities, from Orm to IOC,AOP, ever similar, similar to to even Hashtable t all lowercase, think about a little happy.
In the current spread of programming languages, many languages are gradually beginning to slowly more or less to align, remember the first need to transform a Java EE into. NET, in order to facilitate the direct walk. NET ORM and IOC, so the standard Java Pojo class only need to modify the next suffix for CS to be able to run perfectly in net, hibernate things do not change, directly dropped the past, perfect. At that time, I joked with my colleagues that I could do a tool to convert the C # project into a Java EE, and then Google found that there was such a tool, and quite a few. Perhaps Microsoft is such a convenient Java program for the Smooth migration of apes might
today, every language, in silence like the other side of the alignment, like Java also made play such ror and Django thought framework, but overall, fun, look happy, write comfortable, This article only serves as a gossip, does not participate in any language fighting.
(original) When all programming languages are aligned