到目前为止，我最讨厌我最喜欢的语言的地方是我的选择总是在变。每次我以为我找到了命中注定的那个人，我就会发现我讨厌他的5个(或更多)地方。然后那边的草看起来更绿……

PHP

没有构造函数重载 不一致的函数命名(str_replace，但strtolower) define()不像c++那样逐字替换全局变量。 在与XHTML组合时，像if-语句这样的语句必须以不缩进开始，即使为了保持XHTML缩进一致，XHTML是缩进的。

Ex:

你必须输入:

<?php
if($x == NULL)
{
?>
                     <p><?= $x . ' is null' ?></p>
<?php
}
?>

错误捕获非常糟糕

(不知道为什么又把5号改成了1号，随便了)

JavaScript

Function object syntax: f = new Function( "foo", "bar", "return foo+bar;" ); (It takes n arguments, the first n-1 are arguments for the function, then nth is the actual function, in string form. Which is just silly.) Function arguments can be repeated. f = new Function( "foo", "foo", "return foo;" ); The last repetition is the only one ever used, though: f( "bye", "hi" ) // returns "hi" f( "hi" ) // returns undefined E4X should just die. My users are always complaining that it doesn't work the way they think it will. Let's face it, when you need a page and a half of psuedocode for a setter, it's time to rethink things. A standard notion of stdin/stdout/stderr (and files!) would be nice. null != undefined It's irritating to have to handle them both. Sometimes it's useful, but most languages manage to limp along fine with one.

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个:)

再给c++投一票…仍然是我最喜欢的语言，有几个亲密的追随者——C和Python。以下是我目前最讨厌的名单，排名不分先后:

Plethora of integer types inherited from C - way too many problems caused by signed vs. unsigned mistakes Copy constructors and assignment operators - why can't the compiler create one from the other automatically? Variable argument madness - va_list just doesn't work with objects and I'm so sick of problems created with sprintf(), snprintf(), vsnprintf(), and all of their relatives. Template implementation is required to be fully visible at compile time - I'm thinking of the lack of "export" implementations or at least usable ones Lack of support for properties - I want to have a read-only member like "a.x" that can be read publicly and only assigned internally. I really hate the "val=obj.getX()" and "obj.setX(val)". I really want properties with access control and a consistent syntax.

我有一本书探讨了SNOBOL中的各种项目。第一章探讨了SNOBOL编程和语言的历史和文化，并花了一些时间论证一个优秀的程序员喜欢一种语言不是因为它的缺陷，而是尽管有缺陷。

我最喜欢的语言是Icon/Unicon。但还是有一些事情让我很恼火:

它不是很出名，也不是很受欢迎。 与PHP、Perl、Java等相比，它的库要小得多。数据库访问是通过ODBC完成的，这实际上非常烦人。 对于所有其他出色的列表处理，我想念PHP内置的explosion()和implode()。 它没有表常数。列表，是的，表格，不是。 它是一种编译(实际翻译)语言。