Book Review: Programming PHP 3rd Edition 155
Michael Ross writes "As a hugely popular scripting language with an 18-year history, PHP has been the topic of countless computer language books. One of the most comprehensive offerings has been Programming PHP, published by O'Reilly Media. The first edition appeared in March 2002, and was written by Rasmus Lerdorf (the original developer of PHP) and Kevin Tatroe. A second edition was released in May 2006, and saw the addition of another co-author, Peter MacIntyre. With the many changes to the language during the past seven years, the book has again been updated, to cover all of the major new features made available in version 5 of PHP." Keep reading for the rest of Michael's review.
This third edition was published on 22 February 2013, under the ISBN 978-1449392772, with the same three authors at the helm. At a substantial 540 pages, the information is organized into 17 chapters, each focusing on a particular area of the language and its usage. This material precedes an appendix of almost 130 pages, which serves as a reference for all of the language's built-in functions. In fact, not only could this book suffice as a reference guide, it could also serve as a tutorial, because it is accessible to programmers of all levels, including beginners who have never before worked with PHP. The preface notes that the material assumes only "a working knowledge of HTML." However, the example code seems to also assume that the reader is comfortable with fundamental programming concepts, such as conditionals and loops.
| Programming PHP, 3rd Edition | |
| author | Kevin Tatroe, Peter MacIntyre and Rasmus Lerdorf |
| pages | 540 |
| publisher | O'Reilly Media |
| rating | 8/10 |
| reviewer | Michael Ross |
| ISBN | 978-1449392772 |
| summary | An extensive tutorial of the PHP web programming language. |
To learn more about the book, prospective readers and buyers may wish to visit the publisher's website, where they will find a description of the book, its table of contents, a free copy of its first chapter, and the example code for ten of the chapters. Speaking of formats, the book is available in print and electronic media. (This review is based upon a copy of the print version kindly provided by the publisher.)
The first three chapters explain the bedrock fundamentals of the language, including its lexical structure, data types, variables, expressions, operators, flow-control statements, code inclusion methods, and functions. All of the information appears to be valid, aside from several technical blemishes: In Example 1-1, most of the lines of code are duplicated. Example 1-5, which supposedly creates a PNG file, does not seem to work. The section on constants (page 21) should have mentioned the core predefined constants and also distinguished those from magic ones. The binary literal 0b01100000 is 96, not 1 (page 23). It is claimed that an object is evaluated as false if it contains no values or functions (page 25), and yet: "class C{} assert( new C );." The closure example code (page 29) fails because it includes a function name and no terminating semicolon. The example code in the middle of page 66 contradicts the claim that an inner function "cannot be called from code parsed after the outer function." The example code starting at the end of that page fails because $a in foo() is undefined. Nonetheless, even experienced PHP programmers could pick up knowledge not encountered before, or at least refresh what was learned years ago and since forgotten due to disuse.
The next two chapters explore in detail further essential components of PHP: strings, regular expressions, and arrays. As with the earlier chapters, readers will encounter example code that does not appear to have been tested. For instance, the print_r() output of an object is missing the class name (page 84). On the same page, print_r() and var_dump() of $GLOBALS do indicate "*RECURSION*," but do not loop infinitely or three times, respectively, as claimed. The $record on page 86 is missing its trailing tab character. For these errors and others, it is not clear whether the authors or the technical reviewers are ultimately responsible. Regardless, readers should find useful the tables summarizing regular expression character classes, anchors, quantifiers, and options. On the other hand, the treatment of conditional expressions is sorely in need of examples. Also, readers will be baffled when told that "The preg_match() function takes the same arguments and gives the same return value as the preg_match() function []" (page 112). Lastly, the callback example code is faulty (pages 131, 133, and 141). The sixth chapter, covering object-oriented programming is well-written, aside from the confusing phrase "including it to a different name" (page 160) and the anti-Nietzschean "this will fatal" (page 161).
With Chapter 7, the book shifts gears from the basic underpinnings of PHP to more applied topics, in this case, web techniques — specifically HTTP, global variables, server information, web form processing, sessions, and more. The narrative is quite clear, except when the reader is told that periods in field names are converted to underscores because periods are illegal in PHP variable names (page 178); the connection is not explained. The next chapter looks at server-side data storage, including the topics of PDO, MySQLi, SQLite, and MongoDB. Confusingly, readers are told that the sample SQL database code is available in a file, but they are not told where to find it (http://examples.oreilly.com/0636920012443/).
Chapters 9 through 11 address PHP's support for three specialized file types: graphics, PDF, and XML. The explanations are excellent, and the authors provide numerous examples. The only obvious flaws are in Example 11-1 (page 269), where the echo statement is missing the "<?" and two of the lines have mismatched single and double quotes.
The remaining half dozen chapters cover critical aspects of PHP development. The chapter on security does not attempt to be exhaustive, but instead explains the most common attack vectors and how to block them. The chapter on application techniques discusses code libraries, templating, output buffering and compression, error handling, and performance tuning. Any programmer intrigued by the idea of replacing clunky VBA code with PHP, should be interested in Chapter 14, which explores the differences in running PHP on Windows vs. other platforms, with a brief look at manipulating the contents of Microsoft Word and Excel files using PHP. RESTful web services and XML-RPC are the topics of the next chapter, whose only apparent blemish is that json_encode() does not add spaces between the array values (page 339). The penultimate chapter addresses multiple environments, manual debugging, and the use of an IDE. The last chapter briefly covers PHP support for dates and times, and thus should have been located much earlier in the book, with the other material on fundamental concepts.
Overall, this book is quite approachable. Throughout, one will find programming style recommendations, However, as with any technical work of this size, there are passages that could be made more complete or clear. Occasionally the authors will mention something explained only later — e.g., "short echo tag" (page 60) — which can be frustrating to anyone new to a language.
The concepts of PHP being taught are extensively illustrated with example code. Some of it is concise enough so as not to distract from the narrative flow, but far too many examples involve much more code than necessary. This at first glance might seem to be an advantage, but it actually makes it more difficult for the reader to see the parts of the code relevant to the topic at hand. Also, the authors underutilize whitespace in the code, instead jamming tokens and parentheses together.
In a book of this size, we should not be astonished to find some errata: "Wordpress" (page xv), "try and" (same page; should read "try to"), "tick function registered when register_tick_function()" (55; should read "with" not "when"), "eXtensible" (59), "super-global" (67; should read "superglobal"), "display_classes() function" (vs. "function displayClasses()"; 164), "$var" (294 and 295; should read "$value"), "functions of blocks" (323; should read "functions or blocks"), "retried" (337; should read "retrieved"), and "a.k.a." (350; should read "e.g.").
In terms of the production of the book, like most other O'Reilly titles, this one is nicely put together, with readable font. But sometimes words are jammed together so much that lines appear to be a single word, e.g., "codeitselfbutplentifulenoughthatyoucanusethecommentstotellwhat'shappening" (page 17). Also, the publisher should avoid splitting the function names as if they were English words, e.g., "addc" and "slashes()" on separate lines (page 91). The index is missing some obvious entries, e.g., "closures." Many code snippets are missing the "Example" numbers and captions. This may be fine if the authors do not reference those snippets, but makes it problematic for anyone else to reference them.
Even though this is arguably one of the most comprehensive PHP books on the market, it does not cover all aspects of the language. On page 1, readers learn that PHP can be utilized in three major ways — server-side scripting, command-line scripting, and client-side GUI applications; but only the first is covered in the book. The appendix consumes over 120 pages, and comprises information easily available online in the PHP manual's function reference. Those pages could instead have been devoted to at least introducing command-line scripting and GUI applications. In fact, there are two major changes the authors could take in bringing this book much closer to perfection: Firstly, retest all of the code and root out any technical snafus. Secondly, replace the lengthy appendix with full coverage of the topics of command-line scripting and client-side GUI applications.
Regardless, Programming PHP is both a tutorial and a reference resource packed with information and example code. Benefiting from the author's deep expertise in the language and its usage, the book is the most promising single source for anyone who wishes to learn this ubiquitous web scripting language.
Michael Ross is a freelance web developer and writer.
You can purchase Programming PHP, 3rd Edition from amazon.com. Slashdot welcomes readers' book reviews (sci-fi included) -- to see your own review here, read the book review guidelines, then visit the submission page.
But... (Score:3, Funny)
Re: (Score:3, Insightful)
Even the manual acknowledges it is bad practice and includes the XKCD comic
There are so many languages that try to hide bad programmers. Give me a PHP programmer and his code and I can tell you if he's worth anything, The language lets you code like an idiot. Which is great, because then I can either not hire you or pay you accordingly if I think you have potential.
GOTO is not a part of PHP so you can use it. It's part of PHP so that if you use it, you are immediately fired and blackballed from the indu
Re: (Score:2)
Even the manual acknowledges it is bad practice and includes the XKCD comic
There are so many languages that try to hide bad programmers. Give me a PHP programmer and his code and I can tell you if he's worth anything, The language lets you code like an idiot. Which is great, because then I can either not hire you or pay you accordingly if I think you have potential.
GOTO is not a part of PHP so you can use it. It's part of PHP so that if you use it, you are immediately fired and blackballed from the industry. It's a trap.
I did encounter a piece of code, ages ago, where in a GOTO was the only possible way to accomplish something. They're pretty rare, but in the instance you need the option it is nice knowing it is there.
Re: (Score:1)
Re:But... (Score:5, Informative)
Some newbie actually went on the kernel's mailing list a long time ago, shocked that GOTO's existed and proposed all sorts of lamebrained approaches just to avoid a clean usage of GOTO like this(shamelessly stolen from one of Robert Love's responses):
do A
if (error)
goto out_a;
do B
if (error)
goto out_b;
do C
if (error)
goto out_c;
goto out;
out_c:
undo C
out_b:
undo B:
out_a:
undo A
out:
return ret;
Easy to read, provides clean stack unwinding, avoids blowing out your cache and only branches on error conditions.
Linus was actually nice to this kid, which surprised me because he deserved all the vitriol he got and more.
One the other hand, that a newbie was actually reading Linux source code was pretty amazing to me. But going on the mailing list and chastising experienced kernel programmers was pretty funny.
Djikstra never gave his paper the title "GOTO's considered harmful", I think it was Wirth acting as editor and who is someone you can ignore safely.
His paper was talking about GOTO's that can bounce all over the place, something essentially impossible in C where GOTO's are local in the function(ignoring longjmp). The paper was published several years before C was developed making his paper irrelevant to C style GOTO's.
I think I used GOTO once, in a virtual machine project that ran bytecode for a educational language that teaches parallel programming concepts.
Re:But... (Score:5, Informative)
Re: (Score:2)
AFAIK the Linux kernel is not written in PHP...
Re: (Score:2)
PHP derived from C, the language the linux kernel is written in.
Re: But... (Score:2)
Re: (Score:2)
Then, "the only way to accomplish something without avoiding goto with lamebrained alternatives just for the sake of avoiding goto"
Re: (Score:2)
By "lamebrained" read "actually knows how to code".
Name JUST ONE circumstance where using a Goto in a higher level language isn't the wrong choice.
Just one.
Re: (Score:2)
You may as well omit that long-ass conditional and just say "the simplest way to accomplish something."
Re:But... (Score:5, Insightful)
Indeed. GOTO is not inherently evil. You'll find it used appropriately in some surprising places -- including the Linux Kernel [oracle.com].
When describing a process, the oft-maligned GOTO certainly comes in handy. The over 30 crowd might remember seeing GOTO's in any number of guide books from auto repair to taxes. (The word wasn't always used, sometimes "skip to ..." or "continue with ..." etc.)
That's right: GOTO can actually make things easier to read and understand.
Even in software today, I'm willing to bet even the most ardent anti-GOT zealot has used a GOTO -- and recently at that -- cleverly disguised as a break or return statement.
Re: (Score:2)
Re: (Score:2)
There is no circumstance where a Goto is the "only possible way". I've been coding for 20+ years, and the last time I used a goto was when as a teenager I graduated from BASIC to Pascal.
Literally, computer science style, *all* possible uses with one exception can be replaced.
And that one exception will never occur in PHP code, as its related to system level assembly programming where the CPUs jump-with-return instructions are not appropriate to the task at hand.
Re: (Score:1)
FTFY
Re: (Score:1)
> Give me a PHP programmer and I can tell you he isn't worth anything
FTFY
Show me a programmer as snottily critical of a language as this and I'll show you a programmer who hasn't been one for very long.
Re: (Score:1)
Give me a PHP programmer and I can tell you he isn't worth anything
Zuckerberg is worth billions. PHP was mentioned by name several times in the Facebook movie [wikipedia.org].
When was the last time you heard Python/Perl/Ruby/C++ mentioned in a movie?
Re: (Score:2)
Zuck may own billions, but that doesn't really say anything about his worth as a person.
Re: (Score:2)
lol, because you can't know more than one language, right?
Re: (Score:1)
The goto seems very arbitrary.
And since PHP supports exceptions (as far as I understand) what exactly is the point of the goto?
Literally the only valid use of goto is for error handling, and that is covered by exceptions.
Every single example they have given could be rewritten using standard control flow.
Re: (Score:1)
Literally the only valid use of goto is for error handling, and that is covered by exceptions.
I use goto in C all the time to break out of loops and jump to a cleanup function at the end of the code. Of course C doesn't have exceptions and nobody compiles PHP to the metal AFAIK, so I think you're right.
Look up setjmp()/longjmp() and tell us again if you still think C needs GOTO in place of exception handling.
OTOH, using GOTO so that a procedure has limited nesting and only a single exit point is far preferable to having one with super-deep/complicated nesting and/or lots of different exit points (something a lot of PHP programmers seem prone to).
Re: (Score:3)
The goto seems very arbitrary. And since PHP supports exceptions (as far as I understand) what exactly is the point of the goto? Literally the only valid use of goto is for error handling, and that is covered by exceptions. Every single example they have given could be rewritten using standard control flow.
It used to be worse. Much worse. Cobol used to have this notion of "ALTER X TO PROCEED TO Y" whereby X was a paragraph containing a GOTO statement. After the ALTER statement is executed, the paragraph X code was modified to now transfer control to paragraph Y. So you had no idea where the logic flow was going because it depended upon whether or not the ALTER was executed.
Life was hell.
Re:But... Spiders on drugs (Score:2)
So what you're saying is that PHP is better than COBOL -- hmmm. PHP reminds me of those spider webs made by spiders on different drugs. PHP is like COBOL reimplemented under the influence of which drug, I wonder?
GOTO can be useful (Score:1)
GOTOs can be a useful language feature, improving program speed, size and code clearness, but only when used in a sensible way by a comparably sensible programmer.
Linus Torvalds: http://kerneltrap.org/node/553 [kerneltrap.org] (mirror at the Wayback Machine [archive.org])
Steve McConnell: http://www.stevemcconnell.com/ccgoto.htm [stevemcconnell.com]
Re:Facebook? (Score:5, Interesting)
Re:Facebook? (Score:5, Insightful)
Honestly, I don't understand what all the complaining is about. It just seems like a lot of language snobbery to me. I used PHP on my small website because every cheap web host out there supports it, there's tons of example code, and it's easy to learn if you have a C/C++ background. It seems to work just fine. Is it suitable for a gigantic website like Facebook? I have no idea really, and I don't care, just like I don't care that bash shell scripts probably aren't suitable for writing, for instance, a full-featured application like a spreadsheet or a video editor, as shell scripts work quite well for the things I do use them for.
Re:Facebook? (Score:5, Insightful)
Honestly, I don't understand what all the complaining is about. It just seems like a lot of language snobbery to me.
As someone who works with PHP every working day: It's a language that wasn't designed, it was congealed. Its lack of design is very evident as soon as you start trying to build anything interesting with it. It was something that was created to solve a short-term problem for one guy, and more-or-less accidentally grew into what it is today. What structures it does have are poor attempts at imitating other languages.
Some examples of what went wrong: ...]" like everyone else.
- Arrays and hashes are the same data structure, for no readily apparent reason. Also, the simplest way of using that data structure is "array(a,b,c,...)", not "[a,b,c,
- All variables start with $, in imitation of Perl, but don't use the @ or % prefixes the way Perl does, instead just pretending everything's a scalar even though it's not.
- For a long time, OOP was an afterthought.
- Unlike other scripting languages like Python, Ruby, and Perl, PHP can't figure out which files to include for you when you reference something outside of the current file. Instead, it offers a global facility called an "autoloader" that allows you to write your own code to tell it how to find it, which completely breaks when multiple libraries have competing autoloaders trying to pick up two different classes with the same name.
- Library functions display no consistency whatsoever. Some are camelCase, some are under_scored. Some search functions put the needle before the haystack, some the other way around.
- Some operators are funky: Values can be equal without being the same thing, for example.
- A significant number of errors, instead of generating exceptions that can be caught and handled, generate fatal errors, which crash your application no matter what. By comparison, Perl, Python, Ruby, and Java allow you to handle almost any error.
I could go on, but the point is there's real reasons for hating PHP.
Re:Facebook? (Score:5, Interesting)
Someone did go on, and on, and on, on this topic. Interesting read that makes never want to go near PHP again:
http://me.veekun.com/blog/2012/04/09/php-a-fractal-of-bad-design/ [veekun.com]
Re: (Score:2)
And don't forget his follow-up: http://me.veekun.com/blog/2012/07/28/quick-doesnt-mean-dirty/ [veekun.com]
Re: (Score:2)
Unicode (Score:2)
Please tell us how PHP rocks to handle Unicode...
Re: (Score:2)
How many of these are still problems now, as opposed to in earlier versions of the language/interpreter? Perl is another language that wasn't all that well designed at first, but was added onto later as it grew into popularity and was used in roles that were unthinkable in its early days.
It is pretty obvious that PHP started out small and grew into its present form, which can be seen with the inconsistency with library function names; obviously they didn't want to break compatibility arbitrarily so they st
Re: (Score:2)
PHP Array Short Syntax [php.net]
There are answers to most of your gripes....except search function needle/haystack ordering. That one bugs me too, as I can never remember which function uses which order.
Re: (Score:2)
- Arrays and hashes are the same data structure, for no readily apparent reason. Also, the simplest way of using that data structure is "array(a,b,c,...)", not "[a,b,c, ...]" like everyone else.
So? Does this gripe have any practical implications? Or is it just a whine for a whine's sake? Also, as of PHP 5.4 (which has been March 2012 BTW), you CAN use the [a,b,c] syntax to create arrays.
- All variables start with $, in imitation of Perl, but don't use the @ or % prefixes the way Perl does, instead just pretending everything's a scalar even though it's not.
Again - so what? You presumably learned how PHP variables work, so you're doing OK. Don't worry about Perl when you're using PHP.
- For a long time, OOP was an afterthought.
But it's not an afterthought now. Or are you still using PHP 4?
- Unlike other scripting languages like Python, Ruby, and Perl, PHP can't figure out which files to include for you when you reference something outside of the current file. Instead, it offers a global facility called an "autoloader" that allows you to write your own code to tell it how to find it, which completely breaks when multiple libraries have competing autoloaders trying to pick up two different classes with the same name.
Again,
Re: (Score:2)
Agree... the snobby sophomoric programmers come out and jump on the bandwagon against what is probably the most widely used language to develop websites with, and claim it's not a good language to develop websites in... it's laughable. It's surely not my favorite language, but it does what it needs to do, it does it relatively simply (that seems to be their problem - if it's easy it can't be good), is well supported. When I switched my website scripting from PERL to PHP it was fantastic; now I use python,
Re: (Score:2)
Also, the simplest way of using that data structure is "array(a,b,c,...)", not "[a,b,c, ...]" like everyone else.
So? Does this gripe have any practical implications?
Yes there is: without syntax highlighting, I can't tell at a glance whether I'm looking at a data structure or a function call, I have to read it more carefully.
- All variables start with $, in imitation of Perl, but don't use the @ or % prefixes the way Perl does, instead just pretending everything's a scalar even though it's not.
Again - so what? You presumably learned how PHP variables work, so you're doing OK. Don't worry about Perl when you're using PHP.
It's harder for me to tell at a glance whether I'm dealing with a numeric array, an associative array (what the rest of the world calls a hash), an object, or a scalar value (e.g. a string or integer). To make matters even more challenging, the culture of the PHP community tries to make it so you can hand it any of those and it will try to convert i
Re: (Score:2)
Or sometimes not: For example, I tracked down a fatal error that was occurring because a default argument (an array) was being manipulated inside of a function. It turned out that what PHP was doing was treating that default argument as a static value the first time, and the second time the function was called it was crashing because it was trying to access the first run's value on the stack. I was able to work around it, but that's not a bug in the program, that's a bug in the PHP interpreter.
Wouldn't the
Re: (Score:2)
That's what you might think, but (in at least this version of PHP) this crashed the application (apologies if /. screws up the formatting):
class Foo { ...
public function bar($arg=array()) {
$arg[] = 'bar';
}
}
While this worked fine:
class Foo {
public function bar($arg=null) {
if ($arg === null) {
The list of absuridities just never ends... (Score:5, Insightful)
Honestly, I don't understand what all the complaining is about. It just seems like a lot of language snobbery to me.
As someone who works with PHP every working day: It's a language that wasn't designed, it was congealed. Its lack of design is very evident as soon as you start trying to build anything interesting with it. It was something that was created to solve a short-term problem for one guy, and more-or-less accidentally grew into what it is today. What structures it does have are poor attempts at imitating other languages.
Some examples of what went wrong: - Arrays and hashes are the same data structure, for no readily apparent reason. Also, the simplest way of using that data structure is "array(a,b,c,...)", not "[a,b,c, ...]" like everyone else.
- All variables start with $, in imitation of Perl, but don't use the @ or % prefixes the way Perl does, instead just pretending everything's a scalar even though it's not.
- For a long time, OOP was an afterthought.
- Unlike other scripting languages like Python, Ruby, and Perl, PHP can't figure out which files to include for you when you reference something outside of the current file. Instead, it offers a global facility called an "autoloader" that allows you to write your own code to tell it how to find it, which completely breaks when multiple libraries have competing autoloaders trying to pick up two different classes with the same name.
- Library functions display no consistency whatsoever. Some are camelCase, some are under_scored. Some search functions put the needle before the haystack, some the other way around.
- Some operators are funky: Values can be equal without being the same thing, for example.
- A significant number of errors, instead of generating exceptions that can be caught and handled, generate fatal errors, which crash your application no matter what. By comparison, Perl, Python, Ruby, and Java allow you to handle almost any error.
I could go on, but the point is there's real reasons for hating PHP.
You could go on forever. Every day that I work on PHP code, I discover another absuridity in this moronic language. Here is today's: take the php function intval, which is meant to parse a string and return an integer:
- if you pass it an object, it emits an E_NOTICE and returns 1
- if you pass it NULL, an array(), and perhaps other things, who knows, it returns 0
- if you pass it a garbage string that is not a number it returns 0
- if you pass it a number with garbage appended it returns the number (e.g., "123aaaa" returns 123)
- if you pass it an overly large number it returns MAXINT
Apparently it did not occur to the people designing this that using valid return values to indicate error conditions is not a good idea.
Add to this, the fact that to know what a PHP API function REALLY does, you often have to read the comments under the API documentation page so you can find out of all the weirdnesses and special cases that the documentation does not mention.
Re: (Score:2)
Then perhaps you should be using the companion function is_numeric() on the variable before attempting to convert it and then you wouldn't have this problem of vague return values!
Re: (Score:2)
Then perhaps you should be using the companion function is_numeric() on the variable before attempting to convert it and then you wouldn't have this problem of vague return values!
Sure, there are always ways to get stuff to work despite the language and API's bad design, I myself get stuff done in PHP when I have to and hey, it beats writing machine code by punching holes in punch cards, but that does not mean the design is not bad and harmful to productive development... Unless you can find a rational reason why intval on an object should return 1, while intval on an array returns 0, and for so many other equally absurd decisions in the language, runtime and API. Try giving this a r
Re: (Score:2)
The better question is why are you passing an object or an array into intval? It says right in the docs that you shouldn't pass an object into that function.
If the php API made any sense, intval would either return NULL or raise an exception when you pass it a value that is not a valid number. You cannot use a number (0 or 1 or MAXINT, depending on the input) to indicate an error in a function that has a non-error output domain that includes all integer values.
Re: (Score:3)
Re: (Score:1)
+1 to this.
Re: (Score:2)
The sad part is that both of the two big languages for web development are like this (with JavaScript) being the other one. When you need to write software that's reasonably maintainable, flexible and secure, having a language that's consistent and predictable is pretty much required.
Re: (Score:2)
Better then 'Moose knuckle' (camelToe's fat ugly sister).
Re: (Score:2)
Is it suitable for a gigantic website like Facebook?
Yes. Facebook is actually implemented in PHP. At one point they used a compiler to compile PHP directly to machine code. Today they have an alternative to Zend called the HipHop Virtual Machine [facebook.com] (HHVM.)
Re: (Score:1)
It's also harder to learn how to do things WELL in PHP. PHP is full of gotchas that complicate programs and catch even veteran programmers, ending up as bugs.
It is a bad language as far as languages go. It's ONLY upside, in today's world, is it's ubiquity, which is not really much of a bragging point.
Node, or Python/ruby with a good framework (which unsurprisingly, the php frameworks are now emulating), is a better choice for someone starting a new project, hands down.
Re: (Score:3)
I so know what my next shell script should be.
Re: (Score:1)
Honestly, I don't understand what all the complaining is about. It just seems like a lot of language snobbery to me.
Ah yes, the mark of an amateur. Dismissing concerns about good language design principles as snobbery or elitism.
Only in the amateur world of PHP and in the GOP are things like education considered elitism and should be shunned.
PHP is never the right answer as folks from Facebook learned the hard way. http://www.quora.com/Quora-Infrastructure/Why-did-Quora-choose-Python-for-its-development/answer/Adam-DAngelo [quora.com]
Re: (Score:2)
Re: (Score:3, Informative)
Similar questions:
People still use automobiles outside of Detroit?
People still eat food outside of McDonalds?
People still have sex outside of brothels?
People still say stupid shit outside of anonymous Slashdot comments?
Haters gonna hate (Score:2)
Honestly. If you can't offer a better solution, stop bitching about it. I and others have asked for something other than PHP for website programming over the past few articles and all I hear is bitching about how bad PHP is.
I use perl for sysadmin scripting stuff. I like perl. For sysadmin scripting stuff. It's a fricking pain in the ass to set up and maintain for the creation of web pages though.
[John]
Re: (Score:2)
Never heard of them. Are they better languages than PHP for creating websites?
(Actually I assume they're perl package managers of some sort but it's hard to parse from your answer.)
[John]
Re: (Score:2)
Ahhh, Web Application Frameworks. Not a language but a way of getting Perl to work writing websites. I may have to poke around and check it out but I do want to say that I'm more interested in writing my own stuff than using a framework to mask the work. Most of what I do doesn't require the excess of any of the available libraries. Besides I think frameworks hide the stuff you should know in order to write code well.
Thanks for the pointers though. I will poke around at them.
[John]
Re: (Score:2)
Most of them don't "know" PHP though, they can hack things together in it, but they're blissfully unaware of the hundreds of pitfalls in it that they fall into time and time again.
The problem is that the people who genuinely know PHP, and know those pitfalls well enough to avoid them consistently also know it well enough to know that there are better alternative languages to use instead.
Re: (Score:2)
Erm, people have offered better solutions, that's kind of why they bitch.
I'm very much a best tool for the job type of person but the inherent problem with PHP is that it's really not the best tool for any job any more.
If you want high quality secure scalable web development then you need something like Java, .NET, or C++ if you actually know what you're doing with it because catching errors at compile time is always better than (possibly not) catching them at runtime. Most issues with type conversion must
Languages in job postings are misnomers (Score:1)
If a job advertises they want PHP in pretty short order you are digging around their Perl code. If a job advertises they want .NET pretty soon you are trying to fix MFC code. I've seen this all throughout my career in programming most times these languages that seem easy or are popular...well usually its just a trap. This separates the men from the boys pretty quickly IMO. Cherry-picking is not for professionals and never has been. In the real world you learn this rather quickly if you intend to survive as
Re: (Score:2)
Re: (Score:2)
I don't think that's a bad thing though. Personally I feel a job where I work with multiple languages (and technology stacks) is far more interesting than just working with the same language and framework day in day out for all eternity.
Re: (Score:2)
Ok you hate PHP. But how many other Popular alternatives are out there.
JSP Oracle is the bad guy right.
ASP Microsoft is the bad guy right.
Perl The 1990's called and they want their programming back.
Ruby on Rails, good alternative however it will be hard to find replacement programmers.
Python, Python is my favorite language, however it isn't that good for web.
Re: (Score:3)
There is a nice looking framework for Scala called Play. I think that could be a good alternative. http://www.playframework.com/ [playframework.com]
Re: (Score:2)
How many web hosts support it? That is why PHP still lives on.
Re: (Score:2)
I'm not sure but it should run as long as you have Java. Scala compiles down to Java byte code.
Re: (Score:1)
You can literally run tens or even hundreds of small PHP websites on a 512 MB VPS or even a few larger. You also shouldn't forget about shared hosting, where most of PHP websites are hosted (albeit those are small sites, but they represent majority of all sites written in PHP).
Nonetheless, PHP language is improving and with the number
Re: (Score:1)
Re: (Score:3)
Yeah, only idiots use PHP -- that's why it's only used by 80% of the web [w3techs.com].
Language snobbery benefits no one. Unless you're Chuck Moore, it also makes you look like an idiot who can't form their own opinions.
Re: (Score:3)
it also makes you look like an idiot who can't form their own opinions.
So does using the "but everyone else is doing it" argument.
I've used all kinds of languages for different purposes and the only thing I can say nice about PHP is that it is nearly as ubiquitous as Perl. Otherwise it is neither as capable or well thought out as it's competitors. My personal pet peeve is the inconsistent error handling (some functions just return true/false, some use NULL and false interchangeably, some write their error messages to STDERR, some to STDOUT, most give you no way to programmatic
Re: (Score:2)
So does using the "but everyone else is doing it" argument.
That's not the argument I'm making :)
PHP is ubiquitous. That's certainly an advantage as far as maintaining it's share of the web. However, that didn't happen overnight. PHP is ubiquitous today because it did the job it was designed to do better than competing languages. This is still true today, as evidenced by several "superior" fad-languages failing to gain any ground. If PHP was garbage that no professional would touch, it couldn't have possibility achieved such an astonishing share!
You can critici
Re: (Score:2)
Yeah, only idiots use PHP -- that's why it's only used by 80% of the web
While I agree with your point about language snobbery, popularity doesn't imply user intelligence. There was a time when 80% of the web was written in Comic Sans with green text on a yellow background ;)
Disclaimer: I actually do like PHP, in spite of the inconsistencies that do admittedly plague it.
Re: (Score:2)
Not quite what I meant -- see my other reply. Apparently I can't communicate ideas today.
Re: (Score:2)
Re: (Score:2)
Yup, as stupid as the Facebook bank balance.
Re: (Score:2)
FTFY
Re: (Score:1)
Yes, Perl is a paragon of structure and consistency:
Exactly what the EXPR argument to when does is hard to describe precisely, but in general, it tries to guess what you want done. Sometimes it is interpreted as $_ ~~ EXPR, and sometimes it is not. It also behaves differently when lexically enclosed by a given block than it does when dynamically enclosed by a foreach loop. The rules are far too difficult to understand to be described here. See Experimental Details on given and when later on.
- Perldoc [perl.org]
Re: (Score:1)
Lua + LuaJIT is can be interesting too.
Re: (Score:2)
Dart might be interesting, when they stop changing everything...all the time.
Re: (Score:3)
Re: (Score:2)
I am more familar with Ruby, so I will comment based on that, but my recollection of Python isn't much different. An object in Ruby is a specific type and will never be a different type, you can not coerce it(although you can get the object to return its representation in a different object: to_s, to_a, etc) to anything else and has no casting. You can't get much safe
Python is just fine for the web (Score:2)
Python, Python is my favorite language, however it isn't that good for web.
The standard for making a python application interact with a web server is wsgi, you can run it inside apache with mod_wsgi or run it in a dedicated server such as uwsgi. Or if you want to go asynchronous you can try tornado.
Re: (Score:1)
If you hire actual programmers that have not only domain knowlege but understand computation they will pick up both Ruby and Rails quickly.
Hire programmers, not programming language/framework end-users.
When you are writing a web app you can use whatever you like and there are a lot of good options:
Perl
Python(with or without the various framworks)
Ruby(with or without Rails or Sinatra) & JRuby
Smalltalk
Haskell
Lisp & Cloju
Re: (Score:2)
"JSP Oracle is the bad guy right.
Don't have to use JSPs and don't even really have to go near Oracle. There are fully open source Java stacks.
"ASP Microsoft is the bad guy right."
Truly skilled high quality professionals don't care about fanboyism, they just use the best tool for the job. If that's ASP.NET then so be it.
"Perl The 1990's called and they want their programming back."
I'll let you have that, though I'd argue that Perl is both of a higher quality design in that it's been built with sound academic
Re: (Score:2)
Python, Python is my favorite language, however it isn't that good for web.
Go home, comment. You're drunk.
Django [djangoproject.com], Pylons [pylonsproject.org], Bottle [bottlepy.org], Flask [pocoo.org], TurboGears [turbogears.org], Zope [zope.org], Web2Py [web2py.com]...
And that's just some of the popular frameworks..
Re: (Score:2)
Re:One page book (Score:5, Insightful)
Re: (Score:2)
I'm in the same place having worked on large PHP projects.
It doesn't mean it's a good technology though, it's still shit and if you're starting a project rather than taking one over then there's always a better option to choose than PHP unless the client stubbornly mandates it.
It really is high time PHP was phased out, there's just too many better alternatives out there, which if you're as experienced in other languages as you say I'm sure you already know.
I don't think anyone is saying don't use it if it's
Re:One page book (Score:4, Informative)