The PEAR group recently published New Guidelines for BC breaking releases. The idea is simple, for example one variant would be:
Old API: MyPackage-1.2.tgz
New API: MyPackage_2-0.9.tgz
The PEAR group recently published New Guidelines for BC breaking releases. The idea is simple, for example one variant would be:
Old API: MyPackage-1.2.tgz
New API: MyPackage_2-0.9.tgz
Zak and Georg held a presentation on the new PHP MySQL extension (mysqli) in Hamburg. I’ve attended this presentation where they summarized all the infos about the latest development. Their slides are available online – a must-read for all PHP developers with lots of useful tips!
No, this posting is not about Remote Procedure Calls, it’s about the “island” I currently spend my vacation: Hallig Langeness. I quoted “island”, because geologically, a Hallig is not an island as it consists of sand and has been created by the sea, which would also wash it away over time, if humans had not “fixed” the coast with stones.
Right now, it’s only Zak, Georg Richter, and me who are on Mayenswarft. Derick was with us for some days, as well as Christian and Sabine. Ulf and Jan visited us for a weekend.
Today is our last day, the tide is high, the wind strong and cold (althoug Zak, as a Canadian, feels comfortable with the temperature).
Pictures are available online from Derick and Christian.
We got Internet here (3 persons sharing 56k), no light on the streets (err, “streets”), 120 inhabitants, thousands of birds, one restaurant (yammi food!), no bakery, no supermarket, no speed limits, no police.
Back on track tomorrow, crossing the Baltic Sea with a ferry, and then making our way back to civilization…
… is the question of a current thread being discussed on pear-dev. Discussion mainly circles around “forking” PEAR to make a PEAR2 which might break BC to previous packages, run on PHP5 only, etc. Some quotes:
Stopping in the middle to start new isn’t the best way I think. (Daniel Khan)
Having PEAR 2 is basically the same like the Ferrari F1 Team changing the motor, because the mechanicians aren’t working properly. (Martin Jansen)
The main problem i saw in PEAR since the begining wasnt technical, was as someone said, managerial. I can name a lot of good technical companies/technologies that disappear even being the best option in the
market. Betmax is classical, Netscape is the new one. PEAR? Will not make a big wave if it disapPEAR, looking at the current state of affairs. (S. Rocha)
What actually prevents us from creating a new pear to even better handle upgrade to PHP5 and repair some definite technical issues, etc.? (Tobias Schlitt)
“You heard that? PEAR was so broken they had to start it all over! I am not touching the thing with a 10 feet pole!” (Alexey Borzov)
Personally, I would love to see a new start with packages that consequently use PHP5’s OO features. Who really cares about the PHP4 OO features once he knows what PHP5 can do? Hence, who really cares about the old PEAR if there’s a PEAR for PHP 5? As PHP4 OO is not the best choice for mission critical projects, anyone seriously doing OO with PHP in the future, will use PHP5 and related packages from the new PEAR.
via pear-dev
With the release of PHP 5 beta 2 comes a textfile explaining the new OO features with sample code.
Update: Here is the new link to the Zend Engine 2 features, the above is broken (why has it been removed from php.net?).
Jack Herrington is brave: he argues that PHP is at least as scalable as Java, and he does it on O’Reilly’s ONJava Website… His arguments are quite obvious:
Still not convinced? Consider JSR 223, the effort to turn PHP into the front end for J2EE by porting it to Java. If PHP on top of Java is scalable, then why isn’t PHP on top of C?
Chregu writes about a Jabber Daemon implemented in PHP that communicates with the Jabber server and writes messages to a MySQL DB.
Wez is going to foster contribution to and usage of PECL. Better PECLs, hmm, yammi.
Some postings have emerged that discuss the implementation of threads in PHP. John recently referred to an article published in the English PHP Magazine and Georg wrote some valuable comments.
Shane did some work on a threads extension available in PECL a couple of months ago. The extension is very experimental.
There’s no plan to incorporate multithreading into PHP5 – if we believe the experts 🙂
I am not sure about how SRM can help with multithreading. At least it provides persistency across requests which allows to emulate a multithreading environment yourself in PHP (left aside if it’s a good idea e.g. to implement priority management of “threads” in PHP itself and not the Zend engine). Comments are welcome.
What’s missing is a threads implementation similar to Java or Ruby, especially with features like:
– set and manage the priority of threads
– define threads as daemons
– allow for synchronized threads (see Ruby’s Mutex Class)
Sebastian started work on a PHP Component Model. I am looking forward to see some first results, especially because the envisaged framework will allow for persistence with the help of SRM.