I remember i started here as a bloody noob with opinions like those of "Next-door".
You mean that you called XRP “trusted”, you bought altcoins for “passive income”, and you
advocated programming in PHP?
The part you didn't include in your quoted reply was the single opinion i refered to (including implicit opinion/s).
I should have wrote it a bit different = "opinion" (singular).
Literally the anser to your question: No. I didn't, i didn't do that too, but i was coding in php pretty well on a daily basis, didn't use much of the php5 OOP functionality, though. Php wasn't quite the language to solve most problems, but quick and straightforward unlike perl, which requires more geekyness, and i was advocating perl pretty frequently. As a plus it was working out-of-the-box on most distributions other than windoze, escpecially because windows was quite the exception in the serverside environment(s) i was working at. Good for web based interfaces using persistent socket connections, also when you needed direct access to the OS functions.
I only used compiler langs when i really needed a native binary for a specific platform, which mostly was a desire for windoze targets. Edited Java on *nix machines, didn't like it at all, don't ask me why.
EDIT: Deep inside, i feel it was something about the naming scheme of the classes and methods. #nohomo
Since you took my sarcastic reply too literally, I will reply literally.
The problem with PHP is best summed up in the classic titled “PHP: a fractal of bad design”; I suggest that you read it all:
An analogyI just blurted this out to Mel to explain my frustration and she insisted that I reproduce it here.
I can’t even say what’s wrong with PHP, because— okay. Imagine you have uh, a toolbox. A set of tools. Looks okay, standard stuff in there.
You pull out a screwdriver, and you see it’s one of those weird tri-headed things. Okay, well, that’s not very useful to you, but you guess it comes in handy sometimes.
You pull out the hammer, but to your dismay, it has the claw part on both sides. Still serviceable though, I mean, you can hit nails with the middle of the head holding it sideways.
You pull out the pliers, but they don’t have those serrated surfaces; it’s flat and smooth. That’s less useful, but it still turns bolts well enough, so whatever.
And on you go. Everything in the box is kind of weird and quirky, but maybe not enough to make it completely worthless. And there’s no clear problem with the set as a whole; it still has all the tools.
Now imagine you meet millions of carpenters using this toolbox who tell you “well hey what’s the problem with these tools? They’re all I’ve ever used and they work fine!” And the carpenters show you the houses they’ve built, where every room is a pentagon and the roof is upside-down. And you knock on the front door and it just collapses inwards and they all yell at you for breaking their door.
That’s what’s wrong with PHP.
There is no other language like PHP. It is undoubtedly the worst programming language that has ever achieved widespread usage.
If we were discussing, say, Javascript, I would acknowledge its strong points. Sure, the language has some flaws; sure, the Node ecosystem sucks and the browser ecosystem sucks worse; sure, a large proportion of Javascript “programmers” are clueless copypaste monkeys who should be forbidden from ever touching a computer. But Javascript is not a horrible language, in itself—at least, not in recent ES editions. I even admit that I sometimes enjoy writing Javascript code. And there are some Javascript experts who can do wizardry with it.
PHP is categorically horrible. PHP is an abomination. Next-door’s advocacy of PHP is like
Elon Musk’s claim that Dogecoin is superior to Bitcoin;
* well, it does show that Next-door is as smart and as credible as Elon Musk! Anyway—PHP is bad, bad, bad. End of story.
* Link that I dug up yesterday for other purposes not yet published... lol. (Analogy added with edits.)Hey, i didn't say php isn't a fucking mess!
It just came more naturally to me for inline web scripting, compared to CGI apps, early with php3. I also liked the idea to insert server side code directly into the design of web pages. CSS wasn't as common as today (or even yesterday). I used the php OOP once in an existing project i had to maintain. It died shortly after (not my fault) but it was enough for me to abandon that lousy, incomplete model. With php5 they changed the object model, to a still incomplete one, only to advertise php6 which "will be fully OO", which seemed to take forever, still came out incomplete and seemed like a real mess to me. At this point i abandoned it.
Reminds me a lot of ETH (or IOTA) started as some kind of good idea, ended up as a mess.
EDIT: Finished backreading that scripting language debate.
What have i started?!
I didn't even introduce
intercal yet, though
Even Pascal, Smalltalk or PL/1 would have been enough among the more commonly known failed dialects, i guess.