Hacker News Reader

Hacker News

Comment by jbverschoor | Hacker News Reader

Full thread

jbverschoor

Won’t be long before php is java

View on HN

You mean the most successful enterprise language and 2nd/3rd most used language overall?

TBH, I don't think PHP is going in that direction.

No, just in terms of features and syntax. Too bad you can't remove all the bad stuff from php, or any old tech.

This was one of my requests to that new search engine posted here a few days ago.. Filter on minimum version of technology. Should actually just be a field in stackexchange.. packages/languages references + version. And a marker to set if the information is obsolete.

PHP and Java are indeed superficially similar (this was claimed 20 years ago, too).

You can't get rid of old stuff in the name of BC, but you often simply don't have to use that old stuff. For example, people hate on JavaScript (and PHP too I believe) for the semantics of their "==" operator, but it's a moot point since these languages have had "===" since many years.

If you are enough aware of the differences that you know you should use `===`, the difference becomes moot, because this is not the only unityped footgun on the language, and one of the easiest ones to deal with. The practical problem with `==` is for beginners, and the reason most people refer to it is because it showcases a very large and deep flaw of the language, not because of itself.

> If you are enough aware of the differences that you know you should use `===`

Every beginner knows that because all recent books literally say "don't use ==, use ===", modern IDEs will point it out for you and 1st code review feedback will point it out.

What usage of this moot point showcases for me is mostly author's blind bashing without real knowledge.

If you only know "don't use ==, use ===", you will just fall for the next unityped trap. If you know why you shouldn't use `==`, you know enough so that even if you don't go for `===`, using `==` safely is the least of your problems.

> for the next unityped trap

Many languages are unityped and carry the same problems, yet they are hyped rather than bashed (e.g. Python, Ruby).

> If you know why you shouldn't use `==`, you know enough so that even if you don't go for `===`, using `==` safely is the least of your problems.

You have some weird false dichotomy going on. I'm personally in the state "I remember why == is bad (type coercion ...)" but I don't remember all the details to be able to use == correctly. I bet many people are in a similar situation.

Your two examples are not unityped, and most unityped languages are unityped all the way down and as a consequence do not have the same problems.

> No, just in terms of features and syntax. Too bad you can't remove all the bad stuff from php, or any old tech.

You can, it just takes ages and dedication and will cause a lot of friction. See: Python's changes between 2.x and 3.x, .NET's breaking changes between 1.x and 2.x+

More like COBOL honestly

use swoole/openswoole with php - async away.

Hopefully it's closer to Kotlin or TypeScript

It's not. It's a mess of OOP mind-castles, very much like Java used to be before streams. Nothing to do with the excellent typed functional-ish programming model of TS or Kotlin.

Reply on news.ycombinator.com