Future of PHP 6
Trackbacks
Mind the encodings!
Dealing with character sets and encodings is tough. As long as you're dealing only with English texts you in a luxury situation and can mix utf-8 and iso-8859-1 encoded texts and most (all?) of your tests will work. Some of your users, like me, with str
Dealing with character sets and encodings is tough. As long as you're dealing only with English texts you in a luxury situation and can mix utf-8 and iso-8859-1 encoded texts and most (all?) of your tests will work. Some of your users, like me, with str
Weblog: Johannes Schlüter
Tracked: Mar 28, 03:32
Tracked: Mar 28, 03:32
Now in trunk: Improved interactive shell
A few years ago I used another blog to write about "More PHP power on the command line" almost 5 years later the PHP interactive shell got a major update which went in PHP's trunk. The commit message tells a lot about the improvements: - Im
A few years ago I used another blog to write about "More PHP power on the command line" almost 5 years later the PHP interactive shell got a major update which went in PHP's trunk. The commit message tells a lot about the improvements: - Im
Weblog: Johannes Schlüter
Tracked: May 28, 21:00
Tracked: May 28, 21:00
Jason, you're doing it wrong!
In a few previous blog posts I was already talking about changes in PHP's trunk, like some BC break or some new features, time to continue: JSON is the modern data format used in "AJAX" applications. As the leading language for the Web PHP cou
In a few previous blog posts I was already talking about changes in PHP's trunk, like some BC break or some new features, time to continue: JSON is the modern data format used in "AJAX" applications. As the leading language for the Web PHP cou
Weblog: Johannes Schlüter
Tracked: Jun 03, 19:08
Tracked: Jun 03, 19:08
Friday, March 12. 2010 at 16:46 (Link) (Reply)
Friday, March 12. 2010 at 17:12 (Reply)
Saturday, March 13. 2010 at 00:26 (Link) (Reply)
Saturday, March 13. 2010 at 10:02 (Link) (Reply)
Saturday, March 13. 2010 at 15:32 (Reply)
Wednesday, March 17. 2010 at 00:45 (Reply)
Would the string class be of any character set, to be decided by the user or will it be fixed to say, utf-8? If it's flexible enough, that would be very nice, so we can also use it for binary data etc.
Friday, March 19. 2010 at 07:41 (Link) (Reply)
Tuesday, March 23. 2010 at 21:43 (Link) (Reply)
Wednesday, May 26. 2010 at 08:45 (Link) (Reply)
Sunday, June 6. 2010 at 10:47 (Link) (Reply)
By getting forward momentum going again, we can also put pressure on hosting providers and others who are still stuck on PHP 5.2, 5.0 or even earlier. I'd like to see PHP again viewed as being at least as viable an option for Web development as Ruby or Python. I think one of the keys to making that happen is a series of at least point-level releases (5.4, 5.5, 6.1, etc.), with real, usable improvements in each.
I'd further propose that there be no "official" 6.0 release; we can mark the timeline as "6.0 ('Enterprise')" after the first Space Shuttle (which never flew a mission). Rather, when and if we have a release that is sufficiently different and backwards-incompatible, that should be labelled as 6.1. Incremental improvements to 5.3 should continue the 5.x line. (This approach is being used, for instance, with the Linux kernel, which is likely to stay at 2.6.whatever for the foreseeable future.)
Friday, August 13. 2010 at 16:40 (Link) (Reply)