c# / .net:

Classes should be sealed by default There should be no lock statement - instead, you should have specific locking objects, and there should be methods such as Acquire which return disposable lock tokens. Corollary: there shouldn't be a monitor for every object. GetHashCode() and Equals() shouldn't be in System.Object - not everything's suitable for hashing. Instead, have an IdentityComparer which does the same thing, and keep the IComparer<T>, IComparable<T>, IEqualityComparer<T> and IEquatable<T> interfaces for custom comparisons. Poor support for immutability Poor way of discovering extension methods - it should be a much more conscious decision than just the fact that I'm using a namespace.

这些都是我想出来的，明天问我，我会想出一个不同的5个:)

JavaFX

Type inference sometimes doesn't behave like you would expect, so you often need to explicitly declare the type. def behaves likes const in C and not final in Java you can insert a value in a sequence by accessing an index >= seq.length, which should actually throw a compiler error (according to the reference). if you assign null to a String, it defaults to "". If you assign null to an Integer, a compiler error is thrown (in contrast to what the reference says). handles CheckedExceptions the same way as RuntimeExceptions

C#

No easy way to check if a type is Numeric It means you are probably stuck using most of the microsoft stack, IIS and MSSQL Instead of being a specific tool for a specific problem, C# tries to be a language for every paradigm. Lack of community. Sure, there are starting to be open-source frameworks and libraries for C#. The same ones that have been available to Java developers for years. Hard to find good help. The internet is littered with poor examples of how to solve problems with C#. This goes back to problem #3.

Erlang

没有静态推断 就像在哈斯凯尔发现的一样。这 会导致运行时错误和一个 有认真写代码还是使用 透析器(1)发现 差异。动态类型是 慢的:也被认为是慢的; 与C、Java等语言相比，它几乎是未知的; 的lists(3)模块有时相当精简 我缺少用于列表处理的有用函数 (就像在数据。例如Haskell中的List); 让我在每句话的结尾都加上 在从句中，和。最后是后者。

Python:

1) line continuation syntax: "...\" works, but "...\ " does not, and that trailing space is generally invisible, without unusual eol-marking by editer. 2) a bare 'raise' is invisible in the stack trace, as the stack trace looks like the previous raised exception. 3) slow 4) poor integration into web-servers (mod_python: dead, mod_wsgi: limited scope of operation). This is complicated by 3], requiring daemonization or some sort of memory-persistance to perform well. 5) overly tolerant of mixed tabs and spaces, allowing changes to control flow to sometimes remain hidden. (maybe fixed in recent versions)

但这只是因为VB6毒害了整整一代程序员

我在一个曾经是VB6商店的VB . net商店工作，而在这里工作的每一个曾经是VB6开发人员的人都顽固地拒绝学习任何关于. net的知识。他们编写的代码就像VB6一样，他们的应用程序就像VB6应用程序一样糟糕。我的老板非常不鼓励使用LINQ，因为她担心其他人很难理解，这是事实，因为没有人想要理解它。

我认为如果微软只使用c#，我们会过得更好，这让我很难受，因为我认为花括号远不如VB的冗长结束语句。