3 ms·

This has been reiterated over and over again and is just a bunch of fluff. It doesn't explain why PHP is bad with examples and while I know there are a ton of s

by vecinu 13y ago

This has been reiterated over and over again and is just a bunch of fluff. It doesn't explain why PHP is bad with examples and while I know there are a ton of sites that do, many people including myself have used PHP successfully in the past. I will refer you to an even better quote: 'Software engineers are becoming like "photographers". They spend so much time arguing over the right lens type, focal length, camera body, flash and other sets of tools until they discover they've already missed their opportunity at taking some great shots. Software devs are now doing the same thing, arguing over the tools they use, wasting precious time instead of getting work done.'

jrheard 13y ago
> It doesn't explain why PHP is bad with examples The linked article specifically does explain why PHP is bad, and it does it by providing literally hundreds of specific examples. It's a really impressive essay.
- Osiris 13y ago
  The very first example about @fopen is full of weird stuff about INI file changes and stuff that are not on by default and if someone turns them on they should understand what they are doing.
wtetzner 13y ago
Being able to successfully use something doesn't mean it was a good idea. Even though it's common, I don't think referring to programming languages as tools is actually accurate. A programming language is more like a building material. And this is an important distinction. Let's look at scenario. Say Fred hired Bob to write a program for him. Bob decides to use PHP. After finishing his work, Bob moves on to other projects. A while later, Fred realizes he wants some changes made to his program. So he hires George. George can't make changes to the program in Haskell. He has to modify the PHP source. The reason I bring this up is that the choice of programming language is important, and is not the same as the choice of tools (e.g. your text editor). You can build a house out of paper mache, but chances are you'll end up regretting it.

by vecinu 13y ago

jrheard 13y ago

> It doesn't explain why PHP is bad with examples The linked article specifically does explain why PHP is bad, and it does it by providing literally hundreds of specific examples. It's a really impressive essay.

Osiris 13y ago
The very first example about @fopen is full of weird stuff about INI file changes and stuff that are not on by default and if someone turns them on they should understand what they are doing.

wtetzner 13y ago

Being able to successfully use something doesn't mean it was a good idea. Even though it's common, I don't think referring to programming languages as tools is actually accurate. A programming language is more like a building material. And this is an important distinction. Let's look at scenario. Say Fred hired Bob to write a program for him. Bob decides to use PHP. After finishing his work, Bob moves on to other projects. A while later, Fred realizes he wants some changes made to his program. So he hires George. George can't make changes to the program in Haskell. He has to modify the PHP source. The reason I bring this up is that the choice of programming language is important, and is not the same as the choice of tools (e.g. your text editor). You can build a house out of paper mache, but chances are you'll end up regretting it.