3 ms·
> all library functions being in the global scope Ever used C? > lack of sane naming conventions for those things Absolutely annoying but also fairly minimal
by meritt 13y ago
> all library functions being in the global scope
Ever used C?
> lack of sane naming conventions for those things
Absolutely annoying but also fairly minimal. Mostly an issue in the string & array functions.
> terrible type conversions
Weak typing has to coerce somehow. Javascript is equally "terrible" at times.
> unsafe libraries
Such as? All the major libraries are thread-safe that I'm aware of
> starting php with every request
PHP exists outside of the web, and even in the web environment, you can run it as fastcgi since inception as a persistent daemon and php-fpm is the standard daemon now as well.
> being able to drop raw php right into html templates
I view that as a feature (which is often abused by beginners)
- mavroprovato 13y ago> > all library functions being in the global scope > Ever used C? Come on, this is not a good argument. C is a 70's language, we can do better than that, even in 1995 when PHP came out.
- leokun 13y agoBy unsafe I meant insecure. Also with C you have to import headers.
- riquito 13y ago> Weak typing has to coerce somehow. Javascript is equally "terrible" at times. >>> "0" == false true !!!!!!! >>> "" == false true >>> "" == "0" false and here we lost the transitive relation...
- rmrfrmrf 13y agoGood. We didn't want it anyway!