PHP

几乎每个标准函数都在全局作用域中 不一致的函数参数顺序 不一致的函数命名 不区分大小写的函数 脚本的行为可能会因php.ini文件的不同而有所不同 能够使用未定义的变量 在某些情况下，必须将结果赋值给变量，然后才能在函数中使用它

更主观地说:

动态类型

我刚刚发现，在c#中创建泛型方法时，我不能使用Enum作为类型约束。

微软有一个足够好的解释，但仍然。我疯了

public static T MyFunc<T>(string arg) where T:Enum //wont work :(

PHP

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

Ex:

你必须输入:

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

错误捕获非常糟糕

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

我的常用语言是爪哇语。这就是我讨厌它的地方:

5)。缺少指针 4)。异常捕捉 3)。布尔类型 2)。BigDecimal类型 1)。c#爱好者和Java爱好者

布尔值可以为空。我觉得这是违反直觉的。

BigDecimal是一个库，而不是一个语言特性。我对BigDecimal和Exception捕获的烦恼主要源于编写测试类，这些测试类必须跳过一堆箍才能完成实际工作。我应该澄清一下，我对这些事情很恼火，我不打算游说改变。

JavaScript

Every script is executed in a single global 'namespace'...something which you have to look out for when working with scripts from different sources If a variable is used but hasnt been defined before hand, it is considered a global variable Browser vendors making up standards as they please, making coding for us developers using such a beautiful language harder than it should be Case-Sensitivity - considering that there is no decent IDE for developing js with compile-time checking Workarounds (such as the use of hasOwnProperty method) to perform some, otherwise simple operations.

我知道我迟到了，但恨是永恒的!

Java

Runtime.exec(). So, if I don't manually clear the STDOUT and STDERR buffers, my code will hang? Wow. Die, plz. Null Pointer Exceptions. Responsible programming means I have to treat most objects like they're unexploded bombs, which is kind of a pisser in an object-oriented language. And when the inevitable happens I kinda need to know which object blew up in my face, but Java apparently feels telling me would be cheating. File I/O. Why do I have to jump through this many hoops to read a dang text file? And when copying files, I have to funnel the source file into my code and manually handle the output byte buffer? You're serious? Primitives vs. Primitive Wrappers. Note that Java now has a number of features that allow you to treat primitives and their wrapper objects as interchangeable in some places, but not in others; don't worry, the compiler will let you know which is which. This feels like a hack to work around a fundamentally broketastic design decision. And it is. (EDIT: Actually, the compiler is a much crappier safety net than I thought, particular when doing equality checks. If `a` and `b` are integers, `a == b` is guaranteed to behave as expected only if at least one of them is of type `int`. If they're both type `Integer`, then that statement will do what you think only if the two numbers are between -128 and 127. `Integer a = 1000; Integer b = 1000; return a == b;` will return `false`. Really.) XML. I have this dirt-simple little XML file I need to create and I have to do what?