Slashdot Mirror
Core PHP Programming
The authors of Core PHP Programming have found a marvelous middle ground. Toward the beginning of the book they have a great deal of light, explanatory material as they cover the basics of PHP. As they move towards more advanced topics there is less explanation and a tighter packing of information. At the same time the book has a large number of small code examples throughout, making sure that you know how to use the functions under discussion.
This is the third edition and I must admit that I had not come across it in either the first or second editions, so I have no great way of comparing them in this review. It has certainly been revised to take into account the changes for PHP 5 and examining the table of contents for the second edition on Safari I can see the that the basic structure has remained the same while the book has grown about 300 pages. The addition of Zeev Suraski as co-author can only be to the benefit of the quality of the information, particularly regarding PHP 5.
The book starts with the absolute rock bottom of PHP, the basic data types and operators through to efficiency, debugging and design patterns. Along the way it covers almost all aspects of PHP 5 with a readable reference style. The 'Core' in the title of this book is a key to understanding it. If you're looking for a book with all the code required to handle session management, or user logins and security (to mention two possibilities) then this isn't the book for you. If, however, you are after a book that more than adequately explains the power and nuances of PHP and programming in the language then this is a marvelous volume.
It's broken up into 5 sections: "Programming PHP," which covers the basics of data, control flow and I/O; "Functional Reference," which is 600 odd pages broken up into 12 chapters that seems to cover every PHP function (a check of three sub chapters showed every function mentioned on the topic at PHP.net was also in the book) and does it well with good explanation and code examples; "Algorithms," which details a number of methods of performing routine tasks such as sorting, parsing and generating graphics; and "Software Engineering," devoted to design, efficiency and design patterns; and finally, there are a seven excellent appendices.
Taken as a whole it does a good job of covering the whole language and the ways of using it.
I can imagine it would make a good companion volume to my other favourite PHP volume, PHP and MySQL Web Development, which tends more towards recipes and leaves out the encyclopedic coverage of this book.
Leon Atkinson has a good page for the book that includes a link to download all the code and examples, a link to the Prentice Hall page for those wanting an example chapter or a look at the Table of Contents and some other reviews. His site also has a page for the inevitable errata, currently blank. While I did find only one typo (not in example code) I can't claim to have read every page or run all the code examples.
I'd recommend this volume to anyone who wanted a comprehensive guide to PHP 5. It is probably useful at almost all levels.
You can purchase Core PHP Programming, 3rd Ed. from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
Does one really need a 1000 page reference on PHP? The online documentation is free, downloadable, and quite complete.
TODO: Something witty here...
No PHP sticker from ThinkGeek inside? C'mon! Theres gotta be some incentive to buy it, instead of printing the online stuff.
Frink: Nice try floyd, but you were designed for scrubbing, and scrubbing is what you shall do.
I always print out the manuals, faqs and howtos I read frequently. I also print out important e-mails.
The owls are not what they seem
There is no general alphabetical function list, and even in the function categories the listings aren't always in alphabetic order.
Toward the beginning of the book they have a great deal of light, explanatory material as they cover the basics of PHP. As they move towards more advanced topics there is less explanation and a tighter packing of information.
Hmm.. shouldn't that be the other way 'round? I mean, I prefer to have the easy (self-speaking) topics with a tighter packing of information and less explanation than the hard topics, where I could use all help.
In need of reliable and affordable server monitoring?
Wow...been a while since I've seen a TA reference that didn't really mean to include a '&' inbetween.
Offtopic but vaguely amusing.
No, I'm not selling, but here is a link at O'Reilly's website.
If you know PHP to a certain degree, this book is very useful, and presents real world examples. It is very up to date, and even covers things like PHP OOP and PEAR.
libertarianswag.com
It really is a great book. I have both 2 and 3 editions. Yea, you can use the online PHP help, but this book is a must have for the serious programmer. I guess I'm one of those that like to have dead trees in front of me with lots of little tags hanging out the end.
...you know you've been looking at FORTRAN too long.
God, I feel like this code was carved into stone tablets.
Cretin - a powerful and flexible CD reencoder
I was very excited to get a book that covers PHP5. However, since PHP5 is still changing the book leaves a lot to be desired. There is no information at all on SimpleXML, which will probably be the prefered XML handler once PHP5 is released. When I bought the book I was expecting it to be one of those books that gets worn out from use. However, I haven't touched it in over a month (and I probably bought it 6 weeks ago). I would wait to buy books on PHP5 until PHP5 is out. -Jackson
There's a lot of people who say 'you don't need a book, the online docs are great!'. I disagree.
*Some* books are good (although I think there are too many which repeat the same information, not enough focus on particular topics in the PHP world) and necessary because they can go into greater detail than you get from the online docs.
"What about online tutorials?" Some are good, but having it all in one book, written by only one or two authors (as opposed to wrox-style 15 authors) can help keep a consistent presentation of concepts from beginning to end.
I'm not saying online sucks and all books are great - many PHP books aren't all much more useful than the online docs really. But for those that try to actually teach, rather than reprocess, I think they can be more valuable over time than *just* the online docs.
Personally, I think this 3rd edition is good, although there is, imo, too much reprocessing of the manual. You could cut 200-300 pages out of this book and not miss much of anything. What would be left is worthwhile, though. What's missing in all the reference material is details on what, if any, differences there are between PHP4 and PHP5. If it's there it's in text form, not a standard icon set to alert you of potential differences.
BTW, I have roughly the same arguments for PHP training courses, which we teach (subtle plug). "It's all online!" isn't the best answer for everyone. Many people struggle for hours or days with some concepts with only tutorials and reference pages. Put them in a classroom where they can get immediate feedback on new concepts, and they get it much quicker. Each person learns and adapts to new information in different ways, and classroom training is appropriate for some people, whether it's "only" PHP or something else.
creation science book
I've had this book for awhile, and I do agree that it is on the whole a nice book -- being in its third reprint one has to expect that. However, the book doesn't really cover PHP 5 at all. None of the new extensions such as simplexml, sqlite are discussed (just the Zend Engine 2 stuff). On top of that, the ZE2 stuff is even outdated as it talks about things like Namespaces which were removed from PHP 5.
Studies have shown that IDP occurs in only two dimensions, and is reliably influenced by other periodicals within a distance approaching three meters.
Researchers where able, as an example, to block the IDP of a Sears Craftsman Tool Catalog with the July 1999 issue of Playboy Magazine.
In turn, an unabridged copy of War/Peace required two copies of Lady Chatterley's Lover before the IDP succumbed.
Although ive not done too much with it, PHP seems to be fast becomming the de-facto standard for young programmers getting into true dynamic web development on the server.
.net".
Personally I feel that J2EE and JSP is a more 'enterprise' technology for this kind of development with large transactional systems but the nature of PHP tends to lend itself more to the lightweight, free web development and is supported by a growing number of hosting companies (even free hosting companies).
I do question the need for yet another book on the subject, but i prefer to see up to date copies of books such as this hitting the shelves than "1001 ways to do everything you need with
Kudos to the PHP team.
yes, but....
2 1337 4 u!
If you're after a book that more than adequately explains the power and nuances of PHP and programming in the language then this is a marvelous volume.
Ahh... Total Annihilation. Now there was a game that was already years ahead of its time when it came out.
I gotta agree with the poster above.. O'Reilly's PHP Cookbook is an excellent way to sharpen your PHP skills.
.ini, and then make adjustments in the httpd.conf for each customer. I.e., just let them open files in their own directories. And the OO is simple but effective enough for clear maintainable code. Throw in a PHP accellerator and you've got a great environment.
I've recently gotten back into using PHP for medium-size sites, after a brief period of hating it. I hated the security problems, the "fake" OO, the arbitrary stuff like magic quotes, the procedural functions. However, I've changed my opinion a bit: in security, you can have the PHP engine OFF and very tight in the
PEAR (object-oriented extension library) is pretty cool. If you've never used it, try it out: "wget -O- http://go-pear.org/ | php -q".
And PHP5 looks great, I love the fact that it has exceptions, interfaces, and type hints, that will pretty much kill Java on the medium/small end of the scale. So I decided to start using PHP again.
Anyway, the only good book I've seen is the O'Reilly Cookbook. They totally missed the PHP bandwagon but they redeem themselves with this one. It's clearly written, very thorough, and includes recipes of all levels. I learned a lot about PHP just by reading through the recipes. They usually present one clear way to do everything, plus make some useful discussion on performance and security when appropriate. The authors cleary understand PHP deeply.
And the book is pragmatic, unpretentious, and clearly designed to help you get your work done, rather than present a list of "my language is cooler than yours" tricks. Unlike certain others *cough* Python cookbook *cough*. (Granted, that's also a property of PHP itself).
So if you've got the basics of PHP (which you can glean from the PHP web site or from studying other people's code), try the O'Reilly book. It's probably the only one you'll need until PHP5 comes out.
S'n on my B U B!
problem is: nobody knows
Doesn't PHP documentation actually have a whole bunch of skins for it? Plus it has the notes and comments from other users which is often very handy. I don't have this book but I do have the PHP and MySQL book and it hasn't moved from my shelf since I downloaded a copy of the documentation.
Where's the lol? There's supposed to be a lol in there.
just sometimes a print copy of something is just as convienent (I can't use my laptop for long on an airplane or really want to on a bus). If the PHP crew could clean up some of the nits I have with their docs (including better example code) then I'd be perfectly happy with what is online.
When I started writing PHP apps I bought my share of books. It was great reading material when I was in the, well you know...
When on the train going to and from work, it served as great reading material.
When on vacation, it was great reading material.
What does all that accomplish? Well it prepared me to better understand the online documentation when I needed to use it. Now, I easily go to php.net in order to remember what arguments or how many a function takes, etc...
In my opinion, this is the best PHP book out there right now...
Goal in Life: Learn as much as I can...
Patent nonsense aside, Amazon has it's uses once in awhile. Don't want to pay full price? Buy it used!
There's a Mercedes gap too. I want one and can't afford one, but it's not government's job to do anything about it.
Woah, that's such a rant - you've fitted in:
Perl hatred
C hatred
Style
Slashdot hatred
Slashdot Gates hatred hatred
K&R hatred
Larry Wall hatred
Cobol, Lisp and Fortran love (a computer without cobol is like a cake without mustard)
You've even fitted in Beagle 2.
Sir, I salute you, not least because of the rant you're probably going to post in reply to this.
To get over your hatred, I suggest relaxing, perhaps switch to tea instead of coffee. Spend some more time with your family or signficant other.
(I actually rather like most of your posts, just you seem so angry lately. Chill a bit, please.)
Thank you,
Friendly local AC.
WARNING! GOATSE TROLL!
Contact Me (got tired of viruses emailing me).
I durn beat him down like a sheep bitch! Yee-haw, I's got mah furst postin on that intar-webbie thingie! Mah kin wood shore be prowd!
Naw, I dun din dinn't get the first post. I's lying through mah tooth!
But Tyler Eaves dun got beat down like a bitch, dinne?
No shit, just like those mouth-breathers that sign their .sig twice on emails or message board posts. They should have their computers siezed by the FBI for the good of all americans.
And if they're using PHP to do it, they shouldn't have a license to breed anyway. That's like choosing a Craftsman 14mm hex wrench, because it's a good tool, and then proceeding to castrate yourself with it.
Yes, I demand that Unix be re-written in Lisp. PRONTO!
Hahahaha. Is that sarcasm? I sure hope so.
"Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
Online documentation is also ugly and hard to read.
The documentation on php.net is leaps and bounds better than the documentation on any other website I've found. The user comments are very helpful - quite often, my question is answered by one or more of the comments.
I also print out important e-mails.
You must work at my company, printing email seems to be popular here. Print it out, file it in a drawer. I just don't get it.
I agree with the parent - One big paper weight...
From excellent karma to terible karma with a single +5 funny post...
Granted IIS is losing it and it would be nice to have another language in my tool belt anyways. I guess I should quit the MS evil developer camp and pick up a *nix based language or 2...
:-)
It appears that this book is a good place to start, but anyone have any good intro to PHP book ideas for someone coming fresh out of the MS Camp? Also starting PHP tips and similar experiences appreciated
...in bed
Have you ever looked at the online documentation for PHP? It's gotta be the best docs ever. They have code examples, in-depth discussion of each argument, and user comments at the bottom. Everything is nicely formatted and the information is very easy to get to. After reading Core PHP Programming, I can also state with absolute accuracy that the PHP manual is far easier to read and navigate than their "function reference" section. I think the book should be half the price and should not contain the function reference.
I pretty much started out my programming career on the hot-off-the-press Core PHP book. The online documentation is good as a reference, but for someone getting started Core PHP is well balanced enough so the reader doesn't get crushed by details.
Wore my book out...
"One of my key concerns when reviewing a good book is the pull between information density and a light, easily read style. I believe that as we get further along the learning curve we can sacrifice some readability for density -- we want more facts and less explanation."
You've just described some of the basics of good technical writing. The basic theory of writing good technical documentation is identifying your audience and writing so not only does the document answer the audience's questions and provide usefully comprehensible information, but also refers the more literate and technical readers to more detailed sources.
Anyone aspiring to be a writer - either professional or just notating code - should take a few technical writing classes. There's an industry that's refined the process of technical writing and there's no sense to reinvent the printing press - so to speak.
- Dan
But every version has added on more features. Now instead of a smooth and light templating language, people are now writing templating languages to be parsed by PHP. Gahh! The proper response to all the trolls that insult PHP by saying that it isn't a real language is not "Wait until version 5! It supports class introspection!" Instead, the PHP community should have said that PHP wasn't meant to be a "real" language.
Now that PHP requires a 1000-page book, why should it exist? Why not use Perl, or Python, or C?
I will say that the PHP community is a very friendly and helpful group of people. Perhaps that is because so many PHP developers were previously graphic designers, and so they still remember how daunting programming can be to learn.
--
Long-term effects of Bush deficits
That probably should have been marked as flamebait, but I decided to reply instead. I do agree on your point that "Good code is not about obfuscation gibberish or hax0ring. It's about reusability, stability and portability.". However, that being said, I do think that a language like PHP is great for a young programmer. When you first start programming, all you want to do is write something that works. I don't think anyone can say that the first thing they wrote was beautiful or reusable. Once they have been programming for a while they start to see all the stupid mistakes they have been making and fix them. Your argument is like saying there shouldn't be medical interns because they aren't neuro surgeons yes. Clearly there is a place for both. Writing crappy code then staying up all night fixing it is part of becoming a better programmer. You can right shitty code in any language, and you can right good code in ALMOST any language.
You shouldn't use PHP because future employers take a dim view of drug use.
$31.49 (and free shipping).
'I can't claim to have read every page or run all the code examples'
Well I didn't read the article. But seriously though, what kind of review can you expect from a reviewer who can't be bothered to read the whole book?
Not much wrong with PHP. That wasn't my point. It's just every jackass who copies the function reference guide for [language of the week] then tacks on 400 pages of "this is what an if statement is" does not a good book make.
If you want to learn comp.sci there are better books then some jackass reference manual for a programing language.
In reality you could put the PHP grammar on a few pages or so [the C one takes like 4-5 pages in the K&R book] then proceed to show off examples of PHP being used for practical purposes [e.g. accessing mysql, accepting files, etc, etc].
Tom
Someday, I'll have a real sig.
It covers everything in the PHP5 spec up to about a month and a half ago I think. Had to have a peek inside though, because the cover says it covers 4.x, which is clearly a misprint because it's got all the new OO stuff, SQL Lite and simpleXML stuff in there.
on amazon.
There are better languages if all you want to do is write something that works. Python and Ruby, for two.
"Cuz really you don't need to teach how for loops work and all. If the asshat designing a corporate website doesn't know what a variable, function, statement, [etc] is then they shouldn't be employed."
A corporate web designer's job SHOULD be to make the web site look nice and make it easily navigable. Code is not the first priority. Why pay for a code monkey AND a web monkey if you only need very basic code with a nice layout?
"the book covers PHP5, but since PHP5 is still changing the book leaves a lot to be desired. There is no information at all on SimpleXML, which will probably be the prefered XML handler once PHP5 is released. When I bought the book I was expecting it to be one of those books that gets worn out from use. Personally I would wait to buy books on PHP5 until PHP5 is out.
CB
free ipod and free gmail!
I haven't worked with Ruby, but as far as Python goes, a new programmer shouldn't have to worry about whitespace. I agree that having proper whitespace makes code much easier to read and I wish some of the bastards in my group would format correctly, but for a new programmer it would be hell.
The documentation on php.net is leaps and bounds better than the documentation on any other website I've found. The user comments are very helpful - quite often, my question is answered by one or more of the comments.
:).
Amen, three cheers for whoever maintains it, it's the best I've ever come across.
Just for laughs compare it to the PostgreSQL docs where I believe most user contribute notes are about how lacking the documentation is
What a rotten party, have we run out of beer or something?
"Why pay for a code monkey AND a web monkey if you only need very basic code with a nice layout?"
Because they're two different jobs? One person makes the art and the static HTML, the other programs the dynamic sections which are almost always the parts of a website that get exploited.
By your logic the technical writers should code as well since they're dealing with the application too.
Someday, I'll have a real sig.
Does a book on PHP really teach you how to program? I'm sure there are better, language independent resources/books that can 'teach' better.
"Thanks to the remote control I have the attention span of a gerbil."
I started programming years ago using FORTRAN on old IBM mainframes. An amusing trick on those machines was to pass an actual integer to a subroutine and redefine it. It would work. You could redefine "1" to be "2" and get rather curious results from later calculations. (This won't work with g77).
Most FORTRAN code I had to work with was simply horrid -- huge common blocks and spaghetti code. Bad programming by engineers. Also, "buffer overflows" were possible in the langauge. If FORTAN were the lingua franca of the UNIX world instead of "C" (it was not capable of being so, but it if were), it would be just as full of holes and security issues as "C". Most large FORTRAN code bases are instable in their own way in that large FORTRAN programs crash regularly due to programming errors. The only reason you do not read about these kinds of problems with FORTRAN is because it is not used to write operating systems or user interfaces. FORTRAN crashes are not normally critical. Users learn to work around the errors.
Regardless, I think you are right that there are better languages to teach young programmers. But -- PHP is already here, widely implemented and readily available for use in web pages. So teaching good PHP is a good idea. It is something like teaching sex education to teenagers. You want to emphasis abstinence (don't use PHP as your first languae -- learn programming in a better language), but if you do use PHP, here is how to do it . . . (I don't know that the reviewed book teaches good style or not, hopefully so. Yes, I do think that it is possible to develop a good style for any language in which you work.
1) I loved the objected oriented aspects, but was disheartened to learn most of that code only applies to the latest PHP, which isn't deployed in most ISPs.
2) The index is terrible. Thank God the online docs are good. I've rarely been able to use the book as a reference.
3) I'm probably being dense, but I had trouble finding the sample code online. I expected it on Prentice Hall's website or at least an obvious link. (It's on the author's site)
I'm whining, but I really did like this book and would still recommend it.
bs. a new programmer should have to worry about everything that is going to affect the readability of his code in the future when he's an advanced programmer.
it's hard, very hard to break the bad habits instilled in "new" programmers. get em while they're young. that's why i like the fact that python *forces* good form and whitespace. just the notion that it won't work if it's not properly formatted will carry over to other languages when someone moves on to another language, and good style will as well.
understanding the difference between tabs and spaces isn't something too hard for anyone attempting to learn a programming language to tackle.
the parent is gonna get un-modded for this, but i just had to say something...
Don't dread learning PHP. I applied myself to PHP last spring and, I have to say, it was refreshing and a damn lot of fun.
--Richard
PHP seems to attract everybody under the sun--including horrible, horrible programmers. I've had to maintain PHP written by someone else before, and it wasn't pretty. Far from being pretty, it was some of the ugliest code I've ever seen. And when I looked for help on forums with certain problems I ran into, the responses I received were oftentimes truly amateur hackery.
That's probably why PHP has a bad name. That and magic quotes.
why the fuck is there a sister machine gun slashbox?
The problem is number 3. If the documentation is so complete why are the user comments needed? There have been plenty of times I've seen things in user comments that should have been in the actual documentation. That doesn't seem very complete to me.
The Anti-Blog
What I think is needed are books (or a series of books) geared towards a person who is computer-savvy, is motivated, and wants someone to show them how the stuff is done, without having to go through the low-level beginner stuff. It seems like there are an absence of books that are out there for this group, which I happen to be in.
I think most people who complain about the Python whitespace thing haven't written a line of Python. I'd never used a language where whitespace was significant before, but I haven't had a problem yet that was whitespace-related.
FWIW, though, Ruby is probably the closest thing out there to Python, but uses "end" keywords rather than whitespace to delimit blocks. If you absolutely refuse to use Python because of the whitespace thing, Ruby might be right up your alley.
As far as a new programmer, who isn't biased against whitespace-significant languages from the start, I think the biggest danger with Python is that the programmer will become spoiled and not want to learn anything else.
Game... blouses.
the book leaves a lot to be desired.
The publishers were obviously trying to save money by not processing wood pulp to make the paper for the book.
Using leaves for the pages is a red flag for a publisher cutting corners. Again, thanks for the warning!
I think it has a bad name because things like magic quotes, lack of namespaces and a function_name_for_everything() make it feel like it was written with new programmers in mind.
The Anti-Blog
Why does everyone settle for these two?
Rely on 'bots: AddAll, BookPool
http://tinyurl.com/2p85w
http://tinyurl.com/ys56w (Our Price: $28.50)
Including shipping, Walmart: 26.86
Amazon: $31.49 + shipping
BN: $35.99 + shipping
BN: $34.19 + shipping (for BN members)
For all of the Amazon-BN bigots, send me half of your savings, 'kay?
Not every company can afford to pay a web designer and a web developer.
It's pretty cheap to give the web designer a book and say "read this", especially when there's no sensitive data on the line.
Course, it's probably cheaper to pay some Indian folks to do it.
I have the second edition of this book, and I'm loving it. It's great as a reference to flip through sections when you know what you want to code, but can never remember the function name.
PHP changes so often that it's a bad idea to own books on it. Best practices change from week to week. I would be happy if the zend team stopped introducing undocumented application breaking parsing changes into the most minor of upgrades. Frequent language changes are one of the biggest flaws of PHP.
This is slightly off-topic, but is there a way yet to cache a compiled version of a PHP page (e.g., ASP+ or ASP.NET) so that repeated page views of unaltered code aren't wastefully re-interpreted over and over?
You may want to start writing PHP under IIS -- they play pretty well together, you get a few extra windows goodies and keep using a platform you know while preparing to jump to one that may be less familiar.
Tweet, tweet.
I actually reviewed this book for PHP Magazine [www.php-mag.net] in October.
c pp.html
It's supposed to be published in one of the next few issues.
This book is terrible -- If I were to give it a slashdot review rating -- it would be *3* and that is being generous.
Below is the hyperlink to my review:
http://www.wizardtechnologies.net/reviews/phpmag-
------------------------------
Ray Raspberry
raspberry@b3l33t.org
Such companies then shouldn't be able to process private data. Really that simple. Can't afford a professional you can't do business.
As to your off hand remark about India there are plenty of developers in the States that would gladly code a website. The problem is they demand competitive wages [not slave labour rates].
So yeah, if you're company is small then you outsource for developers. You don't just cut corners and have your janitor develop your website...
Tom
Someday, I'll have a real sig.
Hi,
just asmall note: Zeevs lastname isn't Juraski, as said in the "Book info box" in the author field but it is Suraski.
"Such companies then shouldn't be able to process private data. Really that simple. Can't afford a professional you can't do business."
There is no reason for most websites to deal with anything more than a session identifier to keep your browsing preferences. IF that.
There are also, like any real world programming language, many ways to approach the same problem.
Sometimes there are BAD ways (a function might exist to do something simple and quickly and shouldn't be used as part of a more complex solution)
The online docs don't answer the questions like: .ini files?
What's the best way to read in an apps config file and perhaps even write it back out?
How can I write a random cookie to someone and use that value as a lookup into a database of current state and other information (and expire said info for out-of-date sessions)?
Can I easily use XML for configs rather than
Books can show best practices, hazards in using certain functions, how some suites of functions best interact with other uses, etc. A book may also elide certain functions that are older and perhaps better replicated in newer functions - code waiting to die (once that PHP2 stuff gets redone).
This sort of thing has no place in documentation for a list of functions.
We could call is "user manual" vs. "reference manual". Online docs for PHP are a great reference manual.
Ahh...job security. :)
A corporate web designer's job SHOULD be to make the web site look nice and make it easily navigable. Code is not the first priority. Why pay for a code monkey AND a web monkey if you only need very basic code with a nice layout?
I don't know of any corporate web site that doesn't require programming.
If a site is important and complex enough to require a web designer, it will also require a web programmer.
If you think it's ugly online, it will be ugly when printed out, and just less useful since you won't be able to find anything quite as easily.
Karma: It's all a bunch of tree-huggin' hippy crap!
Because web monkeys suck at making valid HTML. The code monkey should write all the HTML and tag it to death so that the web monkey can just stick to what he knows, either writing CSS or another sort of transform to style the page.
Karma: It's all a bunch of tree-huggin' hippy crap!
It's called HTML::Mason.
Karma: It's all a bunch of tree-huggin' hippy crap!
Yeah but if you're website gets to the point where you need PHP to make it go you should get a professional developer to do it for ya. Even if it's your own data behind the scenes.
Still my main point stands. The bulk of these programming books are just recycles with a new lang behind it.
Tom
Someday, I'll have a real sig.
While I agree with you in theory, have you actually tried to learn PHP from the on-line documentation.
My favorite repeated these goes something like this: "There are two methods to accomplish X. You can do Y or Z. Please note, Z is a recently added feature to work around the security issues with method Y. In this document, we will only spend any amount of time documenting method Y."
I have seen something along these lines a number of places.
6. it could disappear without a trace 7. it could get slashdotted.
Do you even lift?
These aren't the 'roids you're looking for.
Use the dual monitor support: one for documentation and the other for coding. Simple.
Just so you know, I have run across bad Python code before. :-) The programmer who wrote it decided he couldn't be bothered to write functions and classes and instead indented by 5 or 6 tabs. Reading it was quite painful.
I guess the moral of the story is that no matter how well you design a programming language, it won't help any if the programmer is sufficiently stupid/lazy.
Wow, too bad I didn't read this article earlier. I recently bought one of Barnes and Noble's PHP books. (They actually have their own line of books now) It's called PHP: In Easy Steps. It's a super light read (192 pgs), and addresses the simple things like String concatenation, using arrays, and even using MySQL with PHP, all at a brand new cover price of $9.95. The book was written by Mike McGrath. It gets you into USING the language, then you can refer to php.net for specific function information.
C. Griffin
"Can I keep his head for a souvenir?" --Max from Sam 'N Max Freelance Police
After you get in deep shit because of a company mail server losing a mail with a quotation in it, you start printing out every goddamn piece of mail that may or may not get you in trouble.
The owls are not what they seem
The main advantage of a hardcopy: orders of magnitude more dots-per-inch. You can also earmark pages to find the important stuff and enjoy the pure tactile pleasure of handling something concrete.
The owls are not what they seem
You can't earmark pages to find the important stuff. You find the important stuff, then earmark the pages.
I'm not particularly fond of handling something concrete if it's going to make it a bunch more inconvenient to find things. I can find an arbitrary PHP function on the PHP site just by putting its name after php.net in the URL. With a printout, no such luck. With a book, you have to find the index, then find the function, then find the page.
Honestly for a bunch of programmers you think efficiency would come high up the ladder of importance. Oh wait, we're talking about PHP. Scratch that.
Karma: It's all a bunch of tree-huggin' hippy crap!