This thread doesn't really seem to be going anywhere so just retorting there where I believe I can still shed a modicum of light.
On Apr 29, 1:53 pm, Knubo <[email protected]> wrote: > Who says that there must be one way of using a tool? Blaming people > for being stupid when using PHP does not make PHP into crap :) Imagine a programming language that nobody knew except you. Imagine how hard that would be. You couldn't search or ask around for ANYTHING. Now imagine a programming language for 99% of the material you can find online or by asking sort of works but leads to painful gotchas. That'd be a sucky programming language on the whole, even if the language itself is pure gold. That was my point: The community is important, and PHP's community is really REALLY bad at code quality. > I'll happily modify my statement to "fast enough" [...] I *OPENED* my PHP bashing post stating that PHP's slowness is irrelevant in the cases where PHP is used. So, uh, yeah, it generally doesn't matter. Just like I said. But PHP *ISNT* *FAST* which is a claim you hear from time to time and I believe that has been insinuated in this thread as well (saying PHP is used to run wikipedia kinda creates the presumption that PHP must be crazy fast to handle all that traffic. That's not really the truth of the matter, as you seem to agree). The remainder of your post highlights the strengths of PHP in a way that proves how bad it is; most of the things you claimed are good things really aren't once your project grows in complexity a little. But, as usual, if all you're doing is translate SQL to HTML in a very simple one-to-one manner then it'll do just fine, though arguably the rails model is far better at it. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
