PHP Best Practices Guide
-
@dafyre said in PHP Best Practices Guide:
@DustinB3403 said in PHP Best Practices Guide:
@aaronstuder PHP can do it all, but the code will be horrendous and a complete cluster compared to any other programming language.
Not when done correctly, lol.
Correctly = PHP!
-
@travisdh1 said in PHP Best Practices Guide:
@DustinB3403 said in PHP Best Practices Guide:
@aaronstuder PHP can do it all, but the code will be horrendous and a complete cluster compared to any other programming language.
Creating HTML tables in PHP? Shoot me now.
You should be formatting any HTML output from PHP with CSS.... Or better yet, writing the front end purely in HTML, Javascript, and CSS... and let the Javascript deal with the PHP output.
-
@dafyre said in PHP Best Practices Guide:
@travisdh1 said in PHP Best Practices Guide:
@DustinB3403 said in PHP Best Practices Guide:
@aaronstuder PHP can do it all, but the code will be horrendous and a complete cluster compared to any other programming language.
Creating HTML tables in PHP? Shoot me now.
You should be formatting any HTML output from PHP with CSS.... Or better yet, writing the front end purely in HTML, Javascript, and CSS... and let the Javascript deal with the PHP output.
I wish I could ignore PHP entirely.
If going the Javascript route, I'd wonder why you still need PHP at all!
-
@aaronstuder said in PHP Best Practices Guide:
I am sorry, I don't follow... What's wrong with PHP?
Mostly the "problems" are that it is old and written for a different world. It lacks many of the advances of more modern languages. It feels stuck in the late 1980s. They've done some great things with PHP 7 to play catch up, but it is still a very old language.
-
@travisdh1 said in PHP Best Practices Guide:
If going the Javascript route, I'd wonder why you still need PHP at all!
You don't need it at all. Not really any language that you need.
-
@scottalanmiller said in PHP Best Practices Guide:
It feels stuck in the late 1980s.
Really? The 1980's? Get a grip on reality.
-
@JaredBusch said in PHP Best Practices Guide:
@scottalanmiller said in PHP Best Practices Guide:
It feels stuck in the late 1980s.
Really? The 1980's? Get a grip on reality.
What syntactic era do you feel it is from? It feels older than languages we were getting around 1991.
-
Are you saying it feels like the 1970s? That feels a bit much. Fortran 77 was.... 1977 and feels much older. But Perl and Tcl were the late 80s and that's what PHP reminds me of. Even though PHP itself came later it was never designed to be a modern language and feels like an 80s design.
-
@JaredBusch said in PHP Best Practices Guide:
@scottalanmiller said in PHP Best Practices Guide:
It feels stuck in the late 1980s.
Really? The 1980's? Get a grip on reality.
C, C++, Java, and PHP all syntactically feel similar to me... So he may not be far off base, but I don't know when C and C++ were originally made available to the masses.
-
@dafyre said in PHP Best Practices Guide:
@JaredBusch said in PHP Best Practices Guide:
@scottalanmiller said in PHP Best Practices Guide:
It feels stuck in the late 1980s.
Really? The 1980's? Get a grip on reality.
C, C++, Java, and PHP all syntactically feel similar to me... So he may not be far off base, but I don't know when C and C++ were originally made available to the masses.
C around 1970, C++ around 1981. Java was 1995, but is much more advanced than PHP. PHP was also 1995, but it wasn't made by advanced researchers and such, it was a guy looking for a super simple way to make home pages. So that it was a throwback to older language styles from 5 - 10 years earlier is exactly what we would expect. He wasn't trying to reinvent language structure or push elegance or expression, it was a task based simple language. So that it feel like a mix of things like Perl, Tcl and such which were its key inspiration should not be even slightly surprising.
-
I just looked at Wikipedia and Perl and Tcl are specifically listed as two of the main influences of PHP! Nailed it.
