I've been a professional C, Perl, PHP and Python developer.
I'm an ex-sysadmin from the late 20th century.
These days I do more Javascript and CSS and whatnot, and promote UX and accessibility.
I'm (mostly) a PHP developer these days. I've been doing it on-and-off since PHP 3.
I have to look up the order of arguments to common functions all the time because PHP was written by a bunch of people who couldn't agree on anything.
I've been coding for over 20 years now! (WOAH, do I feel old)
I've touched just about every resource imaginable under the Sun (too bad they were bought out by Oracle)
Technically, they did agree on one particular thing: consistency with the underlaying C libraries PHP functions were calling. But these C libraries were never built with each other in mind. PHP was initially "scripted C", and so everything uses those function parameter order. Programming in C and jumping to PHP is natural if you're used to the underlaying libraries, but when taken as a collection, the inconsistency does shine.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm (mostly) a PHP developer these days. I've been doing it on-and-off since PHP 3.
I have to look up the order of arguments to common functions all the time because PHP was written by a bunch of people who couldn't agree on anything.
Thanks for sharing. Bad language design == no mnemonics == look ups, gotcha. :)
Technically, they did agree on one particular thing: consistency with the underlaying C libraries PHP functions were calling. But these C libraries were never built with each other in mind. PHP was initially "scripted C", and so everything uses those function parameter order. Programming in C and jumping to PHP is natural if you're used to the underlaying libraries, but when taken as a collection, the inconsistency does shine.