PHP 5.3 has hit Alpha 3 now, so it was about time I got around to poking at the new features myself, instead of just glancing over and deleting huge flame wars on the internals list of the minutae of the much, er, 'discussed' namespaces implementation.
If you're running WIndows, they have builds for you, but the rest of us instead get to build from source. This was slightly tricky:
This recent post on CNET was forwarded to me by a colleague yesterday. An interesting part of the post is that "only 31 percent of companies surveyed by the analyst house had formal policies for evaluating and procuring open-source software."
Following up on our previous post about rebuilding the ppm build server backend, we finally have flipped the switch for all PPM 4 clients (all ActivePerl 5.10 versions and 5.8 since build 818). The new system is more flexible for us, and provides much better coverage of CPAN modules. You can see the refreshed website, or simply run
"I do not think anyone wants Komodo to add breaks -- that is not what word-wrap does." -- Cory Trese on komodo-discuss March 2002
As someone who uses Komodo mostly to edit text and HTML, my perspective on how an editor should behave differs somewhat from users who spend all day hacking in dynamic languages. One such behavior I find it hard to live without is "auto-wrap", the automatic insertion of line breaks at a pre-defined column.
At some time or another, you've probably worked on a project that just doesn't make it on time, on budget, or both. Don't worry, you're not alone. According to some industry studies, including the Chaos Report recently released by the Standish Group, as many as 65% of software projects fail. OUCH. What went wrong? You tell us... do these sound familiar?
OK, here's the second post in the "How to use ActiveState software in strange ways" vein. I'm writing this post in Komodo. Not that surprising given where I work, but it's interesting how I got from my web-based blog interface to a Komodo buffer.