81–83 of 83 posts
Earlier quoted context omitted.
Counterargument: Do do this if the coding standards for the language/framework you're working in require it. Like WordPress.
Wordpress is a legacy procedural codebase and should not be used as an example of good development practices.
I'd rather it be done by people who care than those that don't.
Don't do this. In languages where accidental assignment is possible (i.e. writing if(a=b) when you meant if(a==b) ), configure the compiler or linter to emit a warning in this situation. For example in C, GCC will complain about this when compiling with -Wall, which you should be using anyway.
The real lesson is for language designers, who for some reason love using equals for assignment. Lisp got it right a hundred years ago and nobody learned.
Earlier quoted context omitted.
Wordpress is a legacy procedural codebase and should not be used as an example of good development practices.
Regardless of your religious convictions, Wordpress still exists and that work has to be done by somebody. I'd rather it be done by people who care than those that don't.