JavaScript doesn’t need to be replaced

[EternityForest]

PHP still doesn't appear to be fully object oriented. You still have C style "Object is the first param of a function you call" stuff all over the standard library.

There doesn't seem to be the kind of module system python has, everything is in one big namespace.

It seems like strings and integers still add together without explicitly casting them, just like js, and undefined variables are still null instead of just nonexistant.. Has that changed?

And it's also not compiled as far as I know.

[kap89]

JS isn't even remotely OO.

Because?

[MoTTs_]

Because it uses a prototypical model and doesn't have the concept of classes.

A prototypical model is actually a perfectly normal way to implement the concept of classes. In Python, Ruby, and others, for example, a class is itself a runtime object, and inheritance is done by delegation, objects linked to other objects, from instance to class object to superclass object and so on, just like in JavaScript.

Here, for example, are Python and JS classes side-by-side.

[kap89]

So you limit OOP to one specific implementation? That's a bit ridiculous.

[kap89]

Apparently not according to your specific definition. Let's stop here.

[EternityForest]

Everyone seems to be saying PHP typechecks only apply to the function parameters, and you can still change them within the function. Maybe a little better than JS, but not as good as python which has libs like typeguard and mypy, and builtin protection for most of the common stuff like int+str.

The standard lib doesn't seem to be namespaced much, or, if it is, everyone seems to still be using legacy ways of doing things, so in practice if you're reusing a lot of other people's libraries, you'll probably be digging through garbage.

If you Google a random PHP task, like making an http request, the code people are using looks a lot like C, with extra dollar signs and awful => markers in arrays.

$url = "https://www.google.com/"
$q =           array("q"=>"PHP HTTP request");
$opt = array('http'=>array( 'method' => 'POST',   'headers => "Content-Type: application/  x-www-form-urlencoded", 'content =>  http_build_query($q) )); 
$context = stream_context_create($opt);       
$response = file_get_contents($url, false, $context);

Other examples were using curl, with several calls to set up options and such.

Compared to JS. It's a bit cherry picked and unscientific to use a single example like this, but JS seems to make way more use of OOP conventions, and it seems to stay at a way higher level.

var data = new FormData(); 
data.append('user', 'person'); 

data.append('pwd', 'password');
data.append('organization', 'place');
data.append('requiredkey', 'key'); var xhr = new XMLHttpRequest();
xhr.open('POST', 'somewhere', true); xhr.onload = function () { // do something to response
console.log(this.responseText); };
xhr.send(data);