4 ms·
Nobody can hate something as strongly as somebody who's spend way too much time looking at it. That, in this case, would be me. Those frameworks and ORMs that
by eropple 15y ago
Nobody can hate something as strongly as somebody who's spend way too much time looking at it. That, in this case, would be me.
Those frameworks and ORMs that you claim as a panacea are generally obfuscatory at best (Symfony2, which is a brilliant example of what you can do with PHP and a cautionary tale of designing a system that makes sense to twelve people, ever) to downright maliciously bad (CodeIgniter, get the hell out of my universe and take Joomla with you).
If you can muddle along with glacially inefficient frameworks (often with APIs that make core PHP seem not all that terrible for a time) and ORMs (personally, I don't use an ORM for anything, and credit where credit's due, PDO is actually a very reasonable solution), more power to you, but some of us (hi) have already been to that dance and realized it wasn't going to work for us. So I do criticize PHP on many fronts, from its psychotic language decisions to it's slapdash internals and it's blatant encouragement of idiotic programming practices. (You can say "nobody in their right mind would use that," but the existence of crapfloods of shitty PHP--hello, Wordpress--suggest that either that's not the case or the biggest PHP projects out there are run by lunatics.)
If I end up writing PHP, invariably I end up grabbing Silex and building the useful bits on top of that. While doing so, I continually wish it was a language where imposing actual application structure wasn't essentially actively discouraged; the outright necessity of shit like call-by-name loses what little error-checking you can otherwise get and the solution to any data storage problem seems to be "MORE ARRAYS!". PHP is a tool where a sufficiently advanced developer finds themselves fighting it as much as using it, and that is a shame. Because it doesn't have to be willfully obnoxious. It just is.
I mean, I went back to Java for my own projects, over continued bashing at PHP. That is a low bar. (But, to be fair, Play makes Java tolerable.)
- Encryptor 15y ago"Nobody can hate something as strongly as somebody who's spend way too much time looking at it". Wrong. You can look at something and not hate it as much as someone who just hates PHP because he/she didn't like the syntax or it didn't fit their needs. "Those frameworks and ORMs [...] are generally obfuscatory at best". This is your opinion, not a fact. Don't state it as a fact, unless you've got concrete examples to prove it. "downright maliciously bad (CodeIgniter [...])". Another opinion with no facts to support it. "glacially inefficient frameworks". Another opinion with no facts supporting it. "it wasn't going to work for us". Good. It works for many other people, you happen to be in a different group. More power to you. "psychotic language decisions". Another opinion stated without any facts or even examples. "slapdash internals". As someone who has developed plugins for PHP, I have to ask you what exactly can be qualified as "slapdash", to the point where it brings PHP's internal code quality below similar products? "blatant encouragement of idiotic programming practices": Please, do share with us which "idiotic programming practices" does PHP, the language, encourage, and other similar languages do not? Otherwise, this is another opinion without any facts to support it. "application structure wasn't essentially actively discouraged". For the thousandth time, learn to provide supporting evidence to your arguments. "the solution to any data storage problem seems to be <<MORE ARRAYS!>>". This statement makes no sense. Here's a counter example: if I had 1TB worth of data which I wanted to save to a MySQL cluster, I would _not_ need more arrays than to store the same data to a single MySQL instance, because the storage layer has nothing to do with in-memory representation of an item (except when the programmer decides to make the two similar, but that has nothing to do with the language). Therefore, your statement is false. "a sufficiently advanced developer, finds themselves fighting it as much as using it". Please provide some evidence. As a counter-example, I can point to Facebook, which probably has "sufficiently advanced developers" that are not fighting with PHP. "I went back to Java". I hope you stay there. In conclusion, I'd like to say that, given your unsupported claims, you seem to not have reached a sufficient level of proficiency with PHP. You did say you spent a lot of time looking "at it", but that doesn't necessarily imply that you understood PHP. All the rhetoric in your comment makes for a decent rant, but it will only appeal to similarly-minded people, who hate PHP because of random, half-brained personal reasons. I wish you a happy life, full of hatred for PHP.
- Joeri 15y ago"If you can muddle along with glacially inefficient frameworks (often with APIs that make core PHP seem not all that terrible for a time) and ORMs (personally, I don't use an ORM for anything, and credit where credit's due, PDO is actually a very reasonable solution), more power to you, but some of us (hi) have already been to that dance and realized it wasn't going to work for us." Count me in as someone who took a look at the frameworks and said "no thanks". I think where the frameworks fail is that they always feel the need to go OO. PHP's design is pretty procedural in essence, because it's not a lot more than an HTTP wrapper with some useful procedures you can call. If you wrap that in an OO layer, by necessity you have to complicate things. I've found the best use of objects in PHP is in support of procedural request handler code. The only framework I use is ZF, because you can easily use it without buying into the whole MVC and routing paradigm.
- Getahobby 15y agoWoah, in one sentence you claim about PHP devs feeling the need to go OO and then the next sentence you extol the virtues of ZF? ZF is all OO, all the time.
- SomeOtherGuy 15y agoHe already answered your question in the post you are replying to: >because you can easily use it without buying into the whole MVC and routing paradigm As much as I think the zend framework is terrible, you can pick and choose whatever bits of it you like and ignore the rest. There's no working around assumptions or anything, it is just a normal way of using the framework.
- maratd 15y ago> it's blatant encouragement of idiotic programming practices PHP doesn't encourage bad programming practices. It simply doesn't encourage good ones. That isn't just semantics, either. There are times when you need to break the rules. They're rare, but they're there. PHP is a language which leaves you that option. If choose to use that optional frequently, then you have nobody to blame but yourself.
- tabbyjabby 15y agoLook, there are a number of criticisms of PHP that the language definitely deserves, but I'm not sure if you've hit on any of the legitimate ones. the outright necessity of shit like call-by-name loses what little error-checking you can otherwise get I'm sorry, but I use PHP everyday, and I rarely find myself needing to use call-by-name, except when it is required by internal functions. Many internal PHP functions that manipulate arrays do require the arrays to be passed by reference, but this doesn't prevent unit testing or error checking at all. I can't find any validity in this complaint and am assuming it is more problem of your coding style than an error inherent in PHP's language design. the solution to any data storage problem seems to be "MORE ARRAYS!" Brilliant observation. This is because arrays in PHP do double or even triple duty. They can be simple number-indexed arrays, they can be associative arrays, and they are internally implemented as hash tables, so they can also act as hash tables. Is your problem a semantic one or one of functionality? PHP is a tool where a sufficiently advanced developer finds themselves fighting it as much as using it, and that is a shame. Sorry I can't be as advanced as you.