3 ms·
It sounds like you've never actually used PHP. Even way back when, you could pick from multiple pre-packaged solutions (XAMPP, WAMP, etc). In windows, the insta
by lhorie 7y ago
It sounds like you've never actually used PHP. Even way back when, you could pick from multiple pre-packaged solutions (XAMPP, WAMP, etc). In windows, the installer was a no-brainer click-through wizard, much like any other random software you'd find on sourceforge or whatever. And not only it would setup apache, but also mysql. Then you could click a button to turn on PHP (so no need to type anything in terminal either). You could also get hosting and upload your PHP files via a browser interface to put your hello world live on the web without ever typing any "code" other than the text "hello world" on a index.php file in notepad. Not even knowledge of version control was required for this form of deployment (though, of course, you can also follow standard industry best practices like with any other mainstream language).
- numlock86 7y ago> you could pick from multiple pre-packaged solutions > like any other random software you'd find on sourceforge or whatever > could click a button to turn on PHP > etc. tl;dr you don't need to know anything. Good summary of why PHP in production "back the days" was usually of very poor quality.
- deleted 7y ago[deleted]
- lhorie 7y ago"Poor quality" comes with the territory of popularity. Everyone talks about Java over-engineering horror stories and the Javascript community even coined the "Javascript fatigue" term to summarize the pervasive quality issues in its ecosystem. But naturally it's perfectly possible to write good quality codebases in those languages.