我偶尔会用我喜欢的PHP，而Python会用得太多。

No namespace; everything is in a kind of very big namespace which is hell in bigger environments Lack of standards when it comes to functions: array functions take a needle as a first argument, haystack as second (see array_search). String functions often take the haystack first, needle second (see strpos). Other functions just use different naming schemes: bin2hex, strtolower, cal_to_jd Some functions have weird return values, out of what is normal: This forces you to have a third variable declared out of nowhere while PHP could efficiently interpret an empty array as false with its type juggling. There are near no other functions doing the same. $var = preg_match_all('/regexp/', $str, $ret); echo $var; //outputs the number of matches print_r($ret); //outputs the matches as an array The language (until PHP6) does its best to respect a near-retarded backward compatibility, making it carry bad practices and functions around when not needed (see mysql_escape_string vs. mysql_real_escape_string). The language evolved from a templating language to a full-backend one. This means anybody can output anything when they want, and it gets abused. You end up with template engines for a templating language... It sucks at importing files. You have 4 different ways to do it (include, include_once, require, require_once), they are all slow, very slow. In fact the whole language is slow. At least, pretty slower than python (even with a framework) and RoR from what I gather.

不过，我仍然喜欢PHP。这是网页开发的电锯:你想要一个小型到中型网站的速度非常快，并确保任何人都可以托管它(尽管配置可能不同)?PHP就在那里，它无处不在，只需要5分钟就可以安装一个完整的LAMP或WAMP堆栈。好吧，我现在要回去用Python工作了……

Emacs Lisp

目前还没有足够的商业市场让人们全职用elisp编码 GNU Emacs vs XEmacs不兼容 Scheme中的嵌套函数很整洁，我希望elisp有[1]的概念 用于简单遍历列表的do循环或其他一些工具不是标准的(当然，您现在可以使用lambda进行映射)[1] (function (lambda(…)))[1]应该有一个简写

当然，Lisp的一个美妙之处在于，用一行代码在你自己的代码中修复这些问题并不难。但这并不是与生俱来的，这让我很恼火。

好的问题;我有点不好意思，因为我想不出更好的东西来恨，但说实话，法官大人，没什么好恨的。

Common Lisp

conditions aren't classes (since classes came later), even though their interface is almost identical some of the names are just weird, e.g., flet / labels (only difference: scope), and defvar / defparameter (only difference: behavior when already defined), or any of the bit-twiddling functions (dpb, ldb, etc.) packages are ... really hard to get right -- every time I think I understand them, they don't do what I want built-in data structures and functions aren't as generic as they could be (e.g., why can't I define my own hash function portably?) multiple namespaces for functions, variables, etc. (I'm not opposed to this in principle, but CL made it too complex; Norvig has said he can't tell from the spec but there appear to be at least 7 namespaces)

PHP:

1)强迫我创造不必要的变量:

$parts = explode('|', $string);
$first = $parts[0];

2) lambdas的实现如此蹩脚，它大致相当于使用eval()，而且如此糟糕，我从未使用过它(参见http://www.php.net/create_function)。

3) try/catch系统只能捕获大约80%可能发生的错误。

4) Regex支持和lambda支持一样蹩脚，因为它必须在常规字符串中编写，这使得最难学的编程工具之一变得困难了三倍。PHP应该是一种“简单”的语言吗?

5)没有办法安全地从$_POST中取出东西，而不写两次或构建自己的函数，或使用'@'操作符:

$x = isset($_POST['foo']['bar']) ? $_POST['foo']['bar'] : null;

6)额外答案:“@”。如果你懒得写正确的代码，那就添加'@'，这对以后调试你的代码的人来说太糟糕了。

PHP

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

Ex:

你必须输入:

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

错误捕获非常糟糕

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

再给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.