Could you explain what is bloated about OOP PHP?

When I write Javascript I don't feel like I need an IDE, but when I write PHP I need a good IDE for imports, getters and setters, stringly-typed frameworks like symfony, "doctrine" annotations. Java at least has some decent free IDEs that can generate the boilerplate that are by far superior to PHPStorm.

> When I write Javascript I don't feel like I need an IDE

Isn't it more like that with Javascript an IDE can't help you much anyway.

I agree completely. And to expand on that, TypeScript with an IDE is a joy to work with in comparison.

They looked at the state of Java OOP at the time and just dumped that in PHP without considering the rather large differences between those languages.

At the time, Java was the popular language and drove a lot of the thought behind language design. Go, Swift and others were not on the stage at the time.

>Did they have to copy Java?

I assume you mean because they both use literal words like "class", "public", "private" in the syntax?

It seems fairly logical to use descriptive syntax to me. See c++, c# as well.

>I agree OOP PHP is way to bloated for a dynamic language.

Ever checked Ruby's or Python's feature list? Or ES7 for that matter?

Sorry I wasn't very clear. I meant that the PHP OOP syntax is just needlessly bloated. Meanwhile ES6 or ES7's syntax actually makes developers' lives easier while still being fairly readable, when you have some coding standards.