Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Digital Ocean Blog:
Getting Ready for PHP 7
Jul 16, 2015 @ 12:31:48

The Digital Ocean blog has posted a guide to help you get ready for PHP7, the next major release of the PHP language. There's a lot of new functionality and changes coming with the release along with plenty of performance and consistency improvements.

2015 has been an important year for PHP. Eleven years after its 5.0 release, a new major version is finally coming our way! PHP 7 is scheduled for release before the end of the year, bringing many new language features and an impressive performance boost. But how this will impact your current PHP codebase? What really changed? How safe is it to update? This post will answer these questions and give you a taste of what’s to come with PHP 7.

They start with a brief look at some of the overall performance improvements PHP7 will introduce and a few things to watch out for that may break with the upgrade (like deprecated features and engine exceptions). From there they get into some of the new language features:

  • New operators (spaceship, null coalesce)
  • Scalar type hinting
  • Return type hinting

They each have brief code examples showing how they'd be put to use but there's also links to other resources with more information if you need them.

tagged: introduction php7 prepare changes deprecate update performance

Link: https://www.digitalocean.com/company/blog/getting-ready-for-php-7/

EngineYard Blog:
What to Expect When You're Expecting: PHP 7, Part 1
Apr 03, 2015 @ 08:28:36

Davey Shafik has posted the first part of a new series about PHP 7 on the Engine Yard blog today - What to Expect When You're Expecting: PHP 7.

As many of you are probably aware, the RFC I mentioned in my PHP 5.0.0 timeline passed with PHP 7 being the agreed upon name for the next major version of PHP. Regardless of your feelings on this topic, PHP 7 is a thing, and it's coming this year! With the RFC for the PHP 7.0 Timeline passing almost unanimously (32 to 2), we have now entered into feature freeze, and we'll see the first release candidate (RC) appearing in mid June. But what does this mean for you?

He gets into some of the details of what you can expect to see in this next major release including:

  • Inconsistency Fixes
  • Performance
  • Backwards Incompatible Changes
  • Scalar Type Hints & Return Types
  • Combined Comparison Operator (spaceship)

He ends the post hinting at other things to come in part two of the series including six other big features you need to know about to upgrade to PHP 7.

tagged: php7 series part1 expecting features changes release

Link: https://blog.engineyard.com/2015/what-to-expect-php-7

Reddit.com:
What changes would you like to see in PHP 7?
Jan 20, 2015 @ 12:51:08

In the /r/php subreddit on Reddit.com a question was posed to the community: What changes would you like to see in PHP 7?. So far there's 80+ answers with a wide variety of responses.

As well as massive performance improvements, PHP 7's change / feature list is already looking great. You can find most of the features that have been accepted or are under discussion on the PHP Dev Wiki: RFCs section. But what changes would make a difference to you? What would you really like to see make it in (already suggested or a new suggestion)?

Here's just a few of the suggestions made by fellow Reddit users:

  • fixing inconsistencies in naming
  • sandboxed eval
  • a complete rework of the standard library
  • the introduction of generics
  • adding enum functionality
  • type aliasing
  • stack traces for fatal errors

Check out the full post for more ideas and feedback from other members of the community too. It's an interesting list of suggestions, some that are even already in the works.

tagged: php7 changes reddit opinion community language feature improvement

Link: http://www.reddit.com/r/PHP/comments/2sx5x3/what_changes_would_you_like_to_see_in_php_7/

Mattias Noback:
Backwards compatible bundle releases
Sep 29, 2014 @ 12:31:09

In his latest post Matthias Noback talks about a problem common to Symfony bundles (and, well, software in general) - dealing with backwards compatibility and breaks that could be introduced with new changes.

With a new bundle release you may want to rename services or parameters, make a service private, change some constructor arguments, change the structure of the bundle configuration, etc. Some of these changes may acually be backwards incompatible changes for the users of that bundle. Luckily, the Symfony DependenyInjection component and Config component both provide you with some options to prevent such backwards compatibility (BC) breaks.

He breaks the post up into a few different kinds of backwards compatibility breaks that could happen and code examples of each:

  • Renaming things
  • Changing visibility
  • Changing values

Each topic also includes methods for preventing issues with older users who maybe aren't using the new features. This includes things like sane default values for new settings, renaming services and creating new extensions for working with new properties.

tagged: symfony bundle backwards compatibility changes prevent rename visibility values

Link: http://php-and-symfony.matthiasnoback.nl/2014/09/backwards-compatible-bundle-releases/

SitePoint PHP Blog:
What to Expect from Yii 2.0
Sep 22, 2014 @ 12:32:17

The SitePoint PHP blog has a new post today from Arno Slatius that talks about some of the features coming in Yii 2.0, a PHP-based MVC framework with a target for a stable release coming very soon.

Yii 2.0 was released into beta last April and the goal for a first stable release was set for the middle of 2014. The GitHub issue list has 300 open issues and 2913 closed while I’m writing this and both numbers are still increasing. The progress to the 2.0RC milestone was at 99%. My guess is that the team is close, but we’ll probably have to wait just a little bit longer. While we’re all waiting, lets take a look at what we can expect by looking at an already available example.

He starts with a "tiny bit of history" about the framework (its origins, the work done on 2.0) and talks about some of the requirements to get it installed and working. He helps you set up a sample project and shows off the Twitter Bootstrap integration, the debug bar and the "Gii" tool that can help generate code automatically (following the conventions of the framework). He finishes off the post with a look at some of the main things that changed in the 2.0 release including moving some method calls to properties, datetime handling, behavior definitions and model/view updates.

tagged: yii v2 introduction tutorial changes requirement install gii history

Link: http://www.sitepoint.com/expect-yii-2-0/

SitePoint PHP Blog:
PHP 5.6 End of Beta
Jun 09, 2014 @ 12:08:15

The SitePoint PHP blog has a new post from editor Bruno Skvorc looking at the final beta for PHP 5.6, the latest bugfix release for this upcoming version. He talks about some of the major changes, security upgrades and other fixes included in the release.

On June 5th 2014, the PHP group announced the fourth and final beta of the 5.6 version. This milestone ends the beta program and begins the RC program (currently planned for June 19th), which will from now on focus exclusively on making sure the version is stable enough for release. As is customary with a beta program, no new features were added since beta 1 – all the releases were bugfix and improvement patches only.

New features coming in PHP 5.6 include exponentiation via the "**" operator, the change of the default character set to UTF-8 and several security updates (based on releasely released vulnerabilities in underlying libraries PHP uses). There are a few backwards compatibility breaks that come with the new release as well as deprecated features and various other smaller updates.

tagged: beta php56 changes features bugfix release

Link: http://www.sitepoint.com/php-5-6-end-beta

WordPress.org:
A New Frontier for Core Development
Aug 07, 2013 @ 10:21:32

WordPress, by far one of the most popular PHP-based applications out there has a new post to their site officially stating a change in core development practices:

In a little over a decade, we’ve made twenty five thousand commits to WordPress. WordPress (along with the web itself) has come a long way, but our development workflow has remained largely the same.

As a part 3.7, I’ll be leading an effort to revamp and streamline our development workflow. We’re going to bring all of our core components - our code, our tests, and our tooling - under one roof. Developers will be able to use and improve the tools we’re already working with day-to-day, and we’ll be able to add new tools to make working with WordPress even easier.

We’re also making sure that any changes are compatible with our current workflow, so you won’t have to change the way you work. These changes won’t break any existing checkouts or scripts that use core.svn.wordpress.org.

The post also details some of the new things they're doing to improve the development and deployment process. This includes the creation of a "develop.svn.wordpress.org" SVN repository to hold all new WordPress development. There's also a new build process involving a tool called "bumpbot" and the new addition of Grunt.

tagged: core development changes build process svn develop

Link: http://make.wordpress.org/core/2013/08/06/a-new-frontier-for-core-development

Robert Eisele's Blog:
PHP Hacking
Jun 10, 2011 @ 07:44:52

Robert Eisele has a new post (and some new source) on his blog today that has gotten the PHP community both up in arms and excited about the potential it offers - a fork of PHP that's been modified to include lots of little improvements for changes in performance, some new PHP functions, usability improvements and changes in the MySQLi/mysqlnd drivers.

It took me a while but here's a new toy. Today I publish my own PHP fork based on the PHP 5.3.6 code base with a few changes that make the everydays developer life more bearable. It includes some of the patches I've already published about 3 years ago, my defcon extension and also my infusion extension plus a good bunch of extra gimmickries.

Updates in his release available on github) include:

  • Hardcoded constants
  • Turn off $_REQUEST variable if it's not needed
  • new methods like str_random, ob_fwrite, sigfig and strcal
  • changes in foreach, strstr and binary number handling
  • updates to MySQLi/mysqlnd to return matched rows and mysqi_return

The community reaction to this fork has been divided - some think the work put into these changes should have been submitted to the main PHP project instead and others see it as a good step forward for the language. Share your thoughts by commenting on the post.

tagged: fork hacking language update changes community

Link:

Phil Sturgeon's Blog:
Upgrading to CodeIgniter 2.0
May 06, 2010 @ 09:54:03

For those that are currently using the stable version of the CodeIgniter framework (1.x) and are wanting to know what they'll need to do to upgrade to the upcoming 2.0 release, Phil Sturgeon has just the guide you're looking for.

I got it all working in a few hours after LOTS of headbanging, mouse throwing and blaspheming. All the bugs I found along the way have since been fixed in the 2.0 branch by the Ellis developers or myself. While this does not mean everything is running perfectly [in PyroCMS] , at the time of writing all the worrying bugs are squashed so it should be safe for us to have a play.

He covers a few things like changes to the model class names, the use of plugins (or how you won't anymore), how they've dropped the validation class, that modular separation won't work out of the box and a few more. You can grab the latest version of the CodeIgniter 2.0 branch from the EllisLab bitbucket account (and contribute back if you find a bug!)

tagged: upgrade codeigniter development changes

Link:

Symfony Project:
symfony 1.0.0 beta 2 released
Dec 21, 2006 @ 08:15:00

The symfony project has announced the release of their latest version - 1.0.0 beta 2:

symfony 1.0.0 beta2 is completely compatible with beta1, so you don't need to launch the upgrade task if your project is already running on beta1.

Updates included with this release include:

  • Better compatibility with PHP 5.0.X
  • PEAR dependency has been removed
  • New COPYRIGHT file and licenses/ directory
  • Phing is now bundled with symfony

tagged: symfony framework beta2 release changes upgrade symfony framework beta2 release changes upgrade

Link: