Let's see
In Java:
import some.crap;
import some.more.crap;
import yet.some.crap;
class SomeMailClass
{
create object 1
create object 2
create object 3
call object 1.somefunction();
call object 2.somefunction.bloated();
call object 3.somefunction.Ihave.lost.interest.already();
blah, blah, blah
}
now, let's do this in PHP.
mail('me@mydomain','Subject',$message,$headers);
In Java:
For the above code, I'll bill out an hour to my client just for writing and compiling the class. Oh wait, there was a compile problem, let's debug...recompile, wait, wait, wait... ok, let's get started on the next part
In PHP:
I sent an email, ok, let's get started on the next part.
I'll bill an hour to my client have something to show for it.
Don't fool yourself, I've seen much Java code with "real Java" embedded into the pages. I've worked on projects that make use of BroadVision, Weblogic, etc... and there seems to always be a need to have logic on the presentation layer.
With PHP, I've been using Smarty, and I've been able to accomplish everything I need to do without the having to put PHP logic on the page.
This argument of presentation/logic separation is hypocritical when it comes from Java developers, because they don't practice what they preach.
When I started reading the article I was not impressed at all. When I finished the article, I only walked away with a small hope -> No crashes.
I've been running Office XP, Visio 2002, Flash MX, and Lotus Notes R5 (plus some small apps like WS_FTP for craps and giggles) on Fedora without any issues other than then Office apps freezing like they do on my Windows OS. I'm using Crossover Office btw... David doesn't seem to be anything new...
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...
Slashdot Mirror
Let's see In Java: import some.crap; import some.more.crap; import yet.some.crap; class SomeMailClass { create object 1 create object 2 create object 3 call object 1.somefunction(); call object 2.somefunction.bloated(); call object 3.somefunction.Ihave.lost.interest.already(); blah, blah, blah } now, let's do this in PHP. mail('me@mydomain','Subject',$message,$headers); In Java: For the above code, I'll bill out an hour to my client just for writing and compiling the class. Oh wait, there was a compile problem, let's debug...recompile, wait, wait, wait... ok, let's get started on the next part In PHP: I sent an email, ok, let's get started on the next part. I'll bill an hour to my client have something to show for it.
Don't fool yourself, I've seen much Java code with "real Java" embedded into the pages. I've worked on projects that make use of BroadVision, Weblogic, etc... and there seems to always be a need to have logic on the presentation layer. With PHP, I've been using Smarty, and I've been able to accomplish everything I need to do without the having to put PHP logic on the page. This argument of presentation/logic separation is hypocritical when it comes from Java developers, because they don't practice what they preach.
When I started reading the article I was not impressed at all. When I finished the article, I only walked away with a small hope -> No crashes. I've been running Office XP, Visio 2002, Flash MX, and Lotus Notes R5 (plus some small apps like WS_FTP for craps and giggles) on Fedora without any issues other than then Office apps freezing like they do on my Windows OS. I'm using Crossover Office btw... David doesn't seem to be anything new...
Well, what I started to was download available documenation onto my laptop. Since I'm always on it, I just fire up a browser and browse the docs...
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...