Jeśli jesteś właścicielem tej strony, możesz wyłączyć reklamę poniżej zmieniając pakiet na PRO lub VIP w panelu naszego hostingu już od 4zł!

Archive for Grudzień, 2013

SitePoint PHP Blog: Best PHP Frameworks for 2014

SitePoint PHP Blog: Best PHP Frameworks for 2014

On the SitePoint PHP blog Bruno Skvorc has posted what could be “best PHP frameworks for 2014“. The results were compiled from the feedback of a survey they recently took during the past week.

We asked these questions to decide which frameworks deserve our attention in 2014 the most. The prerequisite for participation was merely having experience in more than one framework, seeing as it’s pointless to ask someone what their favorite bar was if they’ve only drunk in one place.

In the end, the results showed some interesting trends in the choice of PHP framework and their overall popularity. The three topping the popularity charts were (in this order) Laravel, Phalcon then Symfony2. Other mainstay frameworks like Zend Framework, Yii and CodeIgniter were ranked lower in the list. He goes through the results and provides a bit of background on the feedback, including how much of the original data had to be filtered out for one reason or another. He also includes a list of “noteworthy answers” from various folks responding to the survey. His personal choice? Phalcon because of it’s overall performance and the community around it.

So which framework seems most promising for 2014? Which should you switch to in the new year? Is it worth it? That’s entirely up to you – as always, it depends on your comfort level, the project requirements, and time you have to study new things.

Link: http://www.sitepoint.com/best-php-frameworks-2014/
Source: http://www.phpdeveloper.org/news/20583

<!–
var d = new Date();
r = escape(d.getTime()*Math.random());
document.writeln('’);
//–>

SitePoint PHP Blog: Best PHP Frameworks for 2014

SitePoint PHP Blog: Best PHP Frameworks for 2014

On the SitePoint PHP blog Bruno Skvorc has posted what could be “best PHP frameworks for 2014“. The results were compiled from the feedback of a survey they recently took during the past week.

We asked these questions to decide which frameworks deserve our attention in 2014 the most. The prerequisite for participation was merely having experience in more than one framework, seeing as it’s pointless to ask someone what their favorite bar was if they’ve only drunk in one place.

In the end, the results showed some interesting trends in the choice of PHP framework and their overall popularity. The three topping the popularity charts were (in this order) Laravel, Phalcon then Symfony2. Other mainstay frameworks like Zend Framework, Yii and CodeIgniter were ranked lower in the list. He goes through the results and provides a bit of background on the feedback, including how much of the original data had to be filtered out for one reason or another. He also includes a list of “noteworthy answers” from various folks responding to the survey. His personal choice? Phalcon because of it’s overall performance and the community around it.

So which framework seems most promising for 2014? Which should you switch to in the new year? Is it worth it? That’s entirely up to you – as always, it depends on your comfort level, the project requirements, and time you have to study new things.

Link: http://www.sitepoint.com/best-php-frameworks-2014/
Source: http://www.phpdeveloper.org/news/20583

<!–
var d = new Date();
r = escape(d.getTime()*Math.random());
document.writeln('’);
//–>

Kevin van Zonneveld: It’s Almost 2014 and We Are Still Committing Broken Code

Kevin van Zonneveld: It’s Almost 2014 and We Are Still Committing Broken Code

Kevin van Zonneveld has a new post that, while not PHP specific, does have a handy script that will help you stop committing broken code.

Whatever the reason, it’s almost 2014 and we are still committing broken code. This needs to stop because best case: Travis or Jenkins prevent those errors from hitting production and it’s frustrating to go back and revert/redo that stuff. A waste of your time and state of mind, you were already working on other things. Worst case: your error goes unnoticed and hits production.

To help resolve the problem, he suggests using the “hook” system common to most version control software. In his specific example, he shows the use of a pre-commit hook that fires off a bash script on the files being committed. He includes the full code for this bash script that includes a check for PHP scripts using the built in PHP linter (the “-l” option on the command line). He also includes the commands and updates you’ll need to make to get it installed on git.

Link: http://kvz.io/blog/2013/12/29/one-git-commit-hook-to-rule-them-all/
Source: http://www.phpdeveloper.org/news/20582

<!–
var d = new Date();
r = escape(d.getTime()*Math.random());
document.writeln('’);
//–>

Kevin van Zonneveld: It’s Almost 2014 and We Are Still Committing Broken Code

Kevin van Zonneveld: It’s Almost 2014 and We Are Still Committing Broken Code

Kevin van Zonneveld has a new post that, while not PHP specific, does have a handy script that will help you stop committing broken code.

Whatever the reason, it’s almost 2014 and we are still committing broken code. This needs to stop because best case: Travis or Jenkins prevent those errors from hitting production and it’s frustrating to go back and revert/redo that stuff. A waste of your time and state of mind, you were already working on other things. Worst case: your error goes unnoticed and hits production.

To help resolve the problem, he suggests using the “hook” system common to most version control software. In his specific example, he shows the use of a pre-commit hook that fires off a bash script on the files being committed. He includes the full code for this bash script that includes a check for PHP scripts using the built in PHP linter (the “-l” option on the command line). He also includes the commands and updates you’ll need to make to get it installed on git.

Link: http://kvz.io/blog/2013/12/29/one-git-commit-hook-to-rule-them-all/
Source: http://www.phpdeveloper.org/news/20582

<!–
var d = new Date();
r = escape(d.getTime()*Math.random());
document.writeln('’);
//–>

Community News: Packagist Latest Releases for 12.30.2013

Community News: Packagist Latest Releases for 12.30.2013Recent releases from the Packagist:

Source: http://www.phpdeveloper.org/news/20580

<!–
var d = new Date();
r = escape(d.getTime()*Math.random());
document.writeln('’);
//–>

Community News: Packagist Latest Releases for 12.30.2013

Community News: Packagist Latest Releases for 12.30.2013Recent releases from the Packagist:

Source: http://www.phpdeveloper.org/news/20580

<!–
var d = new Date();
r = escape(d.getTime()*Math.random());
document.writeln('’);
//–>

Community News: Latest PEAR Releases for 12.30.2013

Community News: Latest PEAR Releases for 12.30.2013Latest PEAR Releases:

Source: http://www.phpdeveloper.org/news/20581

<!–
var d = new Date();
r = escape(d.getTime()*Math.random());
document.writeln('’);
//–>

Community News: Latest PEAR Releases for 12.30.2013

Community News: Latest PEAR Releases for 12.30.2013Latest PEAR Releases:

Source: http://www.phpdeveloper.org/news/20581

<!–
var d = new Date();
r = escape(d.getTime()*Math.random());
document.writeln('’);
//–>

Community News: Packagist Latest Releases for 12.29.2013

Community News: Packagist Latest Releases for 12.29.2013Recent releases from the Packagist:

Source: http://www.phpdeveloper.org/news/20579

<!–
var d = new Date();
r = escape(d.getTime()*Math.random());
document.writeln('’);
//–>

Community News: Packagist Latest Releases for 12.29.2013

Community News: Packagist Latest Releases for 12.29.2013Recent releases from the Packagist:

Source: http://www.phpdeveloper.org/news/20579

<!–
var d = new Date();
r = escape(d.getTime()*Math.random());
document.writeln('’);
//–>