(no title)
ilyak | 16 years ago
If he actually spent time reading about languages and designing his own, he would throw in function namespacing and function naming conventions and a good built-in abstraction for database access (with a strong bias against SQL injections and towards placeholders/variable binding from the day one), PHP would come out an okayish language and not an universal hate target.
There are some other blunders that he could just not make. And I'm not even dreaming about template system that makes sense now.
He didn't! Who the hell could do that if he wasn't going.
davidw|16 years ago
ilyak|16 years ago
kailashbadu|16 years ago
davidw|16 years ago
http://en.wikipedia.org/wiki/AOLserver
ilyak|16 years ago
The PHP's default templating (stick code into templates) sucks (unusable for anything serious).
PHP's default routing (/foo/bar.php, lookup the file) sucks (you really really want one entry point for your web app.
PHP's default code layout (one PHP file per page) sucks too.
Idiomatic PHP is unusable! So you'd NEED a framework. Maybe homebrewn one. And if you're going for a framework, why not start with Django or Rails?
Every large-scale project in PHP contains an ad-hoc implementation of at least half of Django.
petervandijck|16 years ago
ilyak|16 years ago
rimantas|16 years ago
ilyak|16 years ago
And every file still starts with <? And if one of them doesn't, then your web app would fail epically because you were gzipping your output into your output stream (one and only one), and this extra space in one of files ruined your gzip.
To be fair, it's wonderful that complex PHP apps ever work. It's a complete surprise to me, I'd say they run-by-accident.