Jacob Santos' Blog: Object Oriented Programming Isn't Easy
547846
In a new post to his blog, Jacob Santos talks about why object oriented programming just "isn't easy" - including a few of his dislikes about OOP in PHP.   Functional developers have it easy. Damn straight and I wonder why so many developers choose to write functions, when they can opt for more beautiful classes instead. [...] It is easy to get functions right, all you have to do is prefix them and name them properly and you're done.   He notes that most people get OOP up to a certain point - that being the "has-a" and "is-a" relationships - where things start flying over their heads. He expresses his dislike of the way that Singletons are used (or not used) and places some of the blame on the tutorial and book authors out there trying to teach novice programmers with analogies that don't make sense in a codign situation.
719619
Krystian Hoffman has posted to his blog today a few reasons (10 to be exact) that he likes and uses PHP. Fortunately, most of them are some of the best reasons for anyone to use the language.   ended up with ten points on why I use PHP and I guess this would be a good post here on my blog, as it seems people like lists in general and maybe I could get some people out there that aren't really sure about whether PHP is good or bad, to get some insight at least.  Here's some of his list:   The PHP Community The (language's) Performance Its Portability It has strong Object-oriented support   Other things got a mention as well - the low learning curve, low cost, included libraries - but the above few seemed the strongest.
642498
But it's not as simple as point-and-click.
541647
On Codewalkers.com today, there's a new tutorial posted concerning some of the looping features PHP has to offer.
256980
A little while back Matthew Turland posted about something that some developers moving over to PHP from more strict languages have an issue with - variable typing - and how its evolved in languages over time.   Without a little background in programming languages or computer science in general, it's entirely possible that typing systems are not something that have crossed your mind. I thought I'd take a blog entry to share some of my thoughts on how itÃ¢ÂÂs affecting the creation and evolution of languages.   He walks through history a bit, mentioning C, Java, Python and PHP and how they differ in their default type handling. He especially focuses on the "blurred line" between strong and weak typing and how some if offers special features to the language that uses the method.
94499
Nefarious Designs continues their object-oriented PHP series with part four posted today, a look at some of the new features that PHP5 brings to the table.    After a welcome break, over the late summer public holiday here in England, here's the final part in my object-oriented PHP series. Sorry about the rather extended pause since "Part 3: Taking Relationships Further".   Having already looked at definition, relationships and taking those relationships further, I'm going to look at how PHP5's new Object Model introduces more advanced functionality.    In this latest part they look at clas constants, abstract classes, object interfaces, and magic methods (including overloading).
141010
Newer computer chips with multiple processors require dauntingly complex software and programmers are having a hard time keeping up.
494845
Stuart Herbert has posted a new book review of a new offering from Packt Publishing - "Learning PHP Data Objects" (by Dennis Popel).    The folks at Packt Publishing sent me a copy of Dennis Popel's "Learning PHP Data Objects" to review. I'd never heard of Packt before, and was intrigued.   He includes a high-level overview of what the book contains, but notes that he couldn't get a hold of the code examples mentioned in the book (no CD and couldn't find it on their site). Overall, he found it a good book - it's a good primer to PDO in PHP, but you'll need to know SQL beforehand to work with it. He suggests that it's more of a one or two time read, though - not much in the way of a reference to come back to.
607777
Sometimes developers just don't think about how much trouble they'd cause with a rewrite of existing software. They think that moving up to the latest and greatest is the way to go, and that it makes perfect sense to say out with the old and in with the new. Aaron Wormus disagrees. Well, sometimes - it depends on the circumstances, really.   At ZendCon I talked about "Planning a PHP 4 to PHP 5 codebase rewrite, a practical approach". The talk was based on my own experience, as well as famous discussion of the topic such as Joel Spolsky's "Things you should never do" and the examination of "famous" platform rewrites.   Aaron gives an example of a large company making a move from a COBOL system out to C for a mission critical system. Based on his tale, they didn't put the thought needed into making this move - new development time, keeping old developers on staff, etc - besides the fact that customers don't like change and making a move to another platform is almost definitely going to be noticed by them.
722662
As both Andrei Zmievski and Clay Loveless mention in new blog posts from each, things in the PHP framework scene are getting a bit out of hand.   Andrei's comments:   I know you might be lusting after Rails for some reason and want to have the fame, the glory, and the dancing girls of DHH, but are we not going to be satisifed until Sourceforge is filled with the object-oriented diarrheal remains of our overblown egos and delusions of grandeur?   And Clay's thoughts:   Build a cool app. Forget about your own personal stamp on the framework world; you missed the boat on that one. But, if you want to make a mark, the world is wide open for new and cool applications. Pick an existing framework, start building your app, and contribute fixes back to that framework's community as you find shortcomings in your needs for your app.   They're both in agreement, and on more that one point. They recommend the best course of action for anyone out there with "the itch" to really work with a framework - fine one of the already established ones and dive right in. It might not be your own code, but you can contribute your own functionality and thoughts into the project and establish your own little niche.
492488
A discussion of how to use frame styles in OOo Writer.
450171
Paul Reinheimer has written up a review of one of the latest offerings from No Starch Press - "Object-Oriented PHP, Concepts, Techniques, and Code".    I'll get this out of the way up front; I approached this book with a completely inaccurate perception of what it was going to give me. I would consider myself an intermediate to advanced php developer, and I was hoping this book would teach me awesome ways to use PHP5's OOP power to make my applications better, faster, and more attractive to women.   That wasn't what this book does. This book introduces OOP, explains why it's useful, and goes through to develop several sample applications to demonstrate OOPs power, and more importantly how to use it.    He goes on to talk about the content/size of the book (relatively thin) including what it covers - beginning OOP, OOP in PHP4 and PHP5, a sample application, and a brief look at some of the more advanced features possible.   His overall opinion of the book is good, but there were two complaints that he had, more of a technical nature than just about the content (like the quality checking of the font size in paragraphs, changing in the middle). He'd still recommend it to those looking to get into OOP in PHP, though.
596569
With a bit of a rebuttal for Harry Fuecks' statement that PHP has a great lack of international support comes this new posting from John Lim at PHPEverywhere.
539271
Terry Chay, a popular speaker at many of the PHP conferences and photog to the geek chic crowd in San Francisco, will be speaking at the upcoming PHP Meetup for the SF PHP group. He'll be giving a talk titled "OOps! The PHP Fear and Loathing Guide to OO Design".   How does the PHP developer in the trenches create powerful object-orientation code? By doing what the PHP's architects did, of course: cherry picking the most pragmatic of OOP principles and patterns! This talk is targeted at the PHP developer who has basic knowledge of PHP OOP syntax but wants to find out where OOP principles can fit into a program.   If you'd like to attend, head over to the meetup page for the event and let them know you're coming. It'll be happening at the CNet Network offices February 7th @ 7pm.
194190
Matthew O'Phinney has two new posts that talk about something object-oriented developers seem to shy away from - globals in their classes and how they can make things more difficult to make "embeddable applications" a reality.   In my previous entry, I ranted about the use of globals in popular PHP applications, and how they make embedding said applications difficult. I develop using object-oriented practices, and can honestly say I can't recall ever having slung a global variable around in my own code. Globals seem hackish to me, and as a result, trying to get applications that use them to behave correctly has been a challenge.   In the first part, he notes an interesting find about the $GLOBALS value and illustrates with a code example how he was able to get around it in his instance (wrapping a Serendipity instance in a Zend Framework app).   In part two, though, and uses another code example to show what kind of issues he was seeing with the $GLOBALS - a script that sets some globals in different instances and echoes the results back out.
660083
Ivo Jansch has a recent post made the other day that takes a look at one of the recent offerings from IBM targeted at PHP developers - the functionality to allow PHP to run on their System i platform.   Some of the developers at Ibuildings are working with PHP on IBM's System-i platform. If that name doesn't ring a bell, it has been called 'iSeries' for a while and it's basically a new name for the old AS/400. [...] Recently IBM and Zend have teamed up to port PHP to the i5/OS operating system. So far this port seems succesful; one of the reasons is perhaps that PHP is easier to adopt by traditional System-i developers than Java, which forces you to learn Object Oriented Programming.   He makes mention of the db2 database extension you can use to access the database as well as a "i5 toolkit" to help with the same. He even links to an article talking about it.
588152
Russ asks: Where's the OpenSocial container API? I love Russ because he cuts through all the BS and gets right to the core, most basic question, and he doesn't care who he pisses off. That's my kind of developer. You can't lie to the compiler, when the bits hit the road, you gotta know what garbage goes in and what garbage comes out.  (Ahh programmer's humor!) In other words, suppose I wanted to compete with Google, MySpace, Plaxo and LinkedIn, well, where's the spec that shows me how to do that? Well, of course I don't know, they aren't communicating with riffraff like me, but I have some experience with this kind of stuff, so I can hazard a guess. If they publish a spec,all kinds of projects will likely get started to enable the API in (just for the sake of argument): Drupal, WordPress, Twitter, Pownce, Jaiku, Scripting News (why not add widgets to a random blog), CNN, The New York Times, well you get the idea. There might be lots of implementations very quickly. And that would be it for changes. It would be frozen de facto, they'd have to live with what they have, which given how quickly it was thrown together, probably isn't very good. Not the kind of stuff you'd like to support for the next decade or two. Or maybe they would break everyone, something guaranteed to make them a lot of enemies, much the way Microsoft did, and they were good at migration of APIs.  Google is good at doing AJAXy web UIs, they make users happy, but they're not very good at APIs. This one is a loser, for sure. That's the answer to Russ's question. It's probably not malice that keeps them from releasing details to everyone outside their club, it's pragmatism. They have to try to hold on to it to keep it from becoming even more of a mess than it already is. Just my opinion, for what it's worth. I've been wrong many times before.