Out of the ashes of a severe personality clash in an open source PHP web application framework project rose a new framework proclaiming that it simply sucks less than all the others. Lithium, otherwise known as li3, is the latest PHP application framework to come onto the scene. I know what you’re saying. *Yawn*.
As far as I can tell, Lithium is trying it’s hardest to be fast, lightweight, and use all the features that PHP 5.3 has to offer. I am unable to use it at work for a variety of reasons (not stable, required PHP 5.3 only, Nate is always picking on me via IM) but I am more interested in the ideas that are coming out of it.
(The blog experiment continues: 1 post every weekday in November and I think I only skipped one, but made up for it with a Saturday post)
Node.js is something I want to use, but I do not know what for
While looking around for conferences to speak at that were within a decent drive of my home, I managed to come into contact with Jason Gilmore, who also sells PHP books via EasyPHPWebsites. He saw that I had written this book and offered to put it up for sale via his site. As a result, the price of the book has gone up by $3 to handle some of the new costs, but I’m much happier with the marketing effort that will be accompanying the book. Jason makes his living doing this sort of thing, so I’m happy to have a mentor for this process. I have plans for future books, some of them not even in PHP.
Yes, my waffling continues. But this time it is NOT with respect to what editor to use, as the one true editor has been configured in such a way to make my life easier. I have a personal project that I have been waffling about building in Python (first as a Django app, now maybe as a web2py app) or in CakePHP, since I would probably be most productive building out something quickly using it.
I received an email this evening that you can now purchase my book through Amazon.com's Marketplace! Awesome news. Check out the link http://tinyurl.com/p5o79u and be sure to add your feedback to the page if you've bought a copy.
(Edit: hrm, link doesn't show up on front page but shows up if you click on the link to this posting...)
Joel Moss (a fellow member of the CakePHP community) has been acting like a bit of a Rails (and Ruby) fanboi as of late. He's doing a series of blog posts proclaiming his love for Ruby. Personally, I loved Rails when I first encountered it. Played around with it. Wrote a web site for my simulation baseball league in it. Then started disliking *some* of the people in the community and are now pretty much ambivalent about Ruby and Rails in general. Great tool, not for me. Python seems to be a better fit for me at least.
Okay, so since the first book has been a pretty good success for me, I've been thinking about writing a second book. Will be the same format: PDF, under 100 pages, selling for between $10 and $20. So that got me to thinking "what topic could I go on and on about like an idiot in regards to programming and CakePHP in general?"
I've become a believer in Test Driven Development and TATFT practices (thanks to Giles Bowkett for his blog posts espousing the concept. So why not combine that with my knowledge (no jokes from Nate allowed) of CakePHP and produce another inexpensive book. Thus, the seeds of "Test Driven Development Using CakePHP" have been planted in my mind.
For those not following along on Twitter, the first month of sales of my CakePHP book have been a success: 70 PDF's and 5 print-on-demand copies via Lulu.com. A big thanks to everyone who has purchased a copy. My next thought has been a book about doing Test Driven Development using CakePHP, but perhaps that is just wishcasting.
Holy moley, has it been almost a year since I blogged about a potential CakePHP deployment task. Since a few people have hit me up in Twitter and in the comments for that blog post, I thought I would share my progress on this task. To be blunt, I decided it was a waste of time to do it.
Why? Well, there plenty of options out there to help you with application deployment already. I talked about many of them in the talk I gave at PHPQuebec back in March. In the end, there is no reason to NOT use an existing tool to handle this other than you cannot (or in some cases will not) use one of these tools. I picked Capistrano because:
The book is doing quite well, thanks. 42 copies sold as I type this. I am going to give away one of my "Framework Apocalypse" t-shirts to one lucky random customer when I get to 100. Feedback has been great, so spread the word about the book! As Matt Curry pointed out in his review of my book, don't let the name fool you. It could've been subtitled "how to think like a CakePHP developer".
So, I have a few questions for the lazyweb (aka my awesome readers). I'm hoping they can point me in the right direction.: