dscrd
Joined 14 years ago
Joined 14 years ago
2. That Go is designed as a programming language.
I'm being serious. Unless you have Facebook's resources (and probably not even then) DO NOT USE PHP FOR ANYTHING THAT REQUIRES SECURITY! If you are, start a migration process today. Whatever you think it'll cost, it'll be worth it.
If you cannot decide from the billions of choices out there, go with Go. It's hardly perfect, but way better and simple.
Well, if you like PHP, how could you like language arguments? After all, they always end up destroying your beliefs.
"There are many" equals "almost all are bad".
I don't quite see how this might be a problem. Does the author think those people would be less great in another environment? Does PHP own these people?
"Often times, people are just complaining about PHP because it’s a popular thing to do."
No. We do not complain about PHP because it's popular. We complain about PHP because it sucks and we are forced to use it.
Many of the so-called 4th generation languages (i.e. business shits derived from Cobol with DB support bolted in) are totally crazy in this sense. Not only are identifiers often case insensitive, they can also be abbreviated!
Yet people make massive amounts of money with them.
Python isn't the fastest dog out there, but doesn't fare so badly with the abstractions, and its OO style suits a dynamic language better. It doesn't try to be a Java.
Neither language will give you much protection against programming errors, nor optimize your code very well like many of the new hip languages (Rust, Go, Nim) do.
Proof is right there in the article. To have PHP on the live server is a security risk, period.