Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
In silex's web page, it says that the stable version of siles is 1.3 but silex-skeleton uses version 2 of silex, is this recommended?
Silex 2.0 is not stable yet, in fact is a dev-master. The bigger problem is that a dev-master can change at any time. Unlike a stable version, it may be that one day you will do composer update and your application will stop working for some reason.
It is always preferable stable versions, but you can also developed you application in sync with the branch master of silex.
For your sake and the sake of your team don't do it.
I have made the mistake of putting one of my big projects back in time of Symfony2.0-alpha (or was it beta, not sure). The documentation was scarce, it was unstable for some use-cases - I wen't thought hell and back.
Projects are marked unstable for a reason - they should not be used in production until the devs make sable release.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 11 months ago.
Improve this question
I need to upgrade PHP version of my project. It is PHP5.6 and I want to upgrade it to PHP8.1. I tried to search for such information but couldn't find it, thus, I want to ask. Is it better to upgrade directly from PHP5.6 to PHP8.1, or step by step (PHP5.6 -> PHP7.0, PHP7.0 -> PHP7.1, PHP7.1->PHP7.2 and etc until I reach PHP8.1)?
Upgrading step by step can help you to see what is deprecated by following the logs files and then review the code.
I have recently been made aware of this tool which ostensibly makes this process much easier. Note that I have not used it myself and as such can't speak to how well it works. It looks to be a FOSS project though which is good.
Website: https://getrector.org/
Github: https://github.com/rectorphp/rector
Updating manually as per the guides provided by vee will likely give you better understanding of the benefit each upgrade offers as well as maintaining full control over your project.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 1 year ago.
Improve this question
I have a legacy application which uses
Symfony 1_4
PHP 5.3
MySQL 5.6
Client is asking for an upgrade of all the tech stack to the latest.
Symfony 5
PHP 8
MySQL 8
How can I do this upgrade with minimum effort ?
A solution required without re-writing the whole application.
Upgraded application's security should be major feature
Upgrading from such an old version to the latest version is most likely never going to work.
I suggest rebuilding the application in Symfony 5 manually, it will probably save you a lot time and effort.
You can try to reuse as much business logic as you can.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I developed in PHP for a long time without a framework, I just use PDO for help me with connection database. But now I decided to learn about Zend Framework to increase my productivity, to avoid repetitious code.
I work with Java WEB too, (Hibernate/JPA + JSF + Spring + Maven) that make my work more easy and organized, and I would like to bring it to PHP too.
So my big doubt is: I should starting with ZendFramework 1 or ZendFramework 2? I saw a lot of companies requiring knowledge about ZendFramework 1.
Zend Framework 1 is a dying product. It is the older Version of the Framework and Version 2 has already being developed with Version 3 being on it's way for later 2014 / early 2015 approximately. The reason for companies still requiring ZF1 knowledge is due to their old codebase.
Many companies are starting to re-write their products using newer frameworks to gain the advantages of the newer ones.
With this in mind: clearly go for ZF2 (or any other new fully OOP/MVC Framework). Once you master it, you'll be able to read ZF1 code just as well and you can easily adapt into any other Framework that your company may require.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
We are about to start a new project and we want to use Yii for it. After reading Yii website, I found out that the release date for Yii 2 beta has been set to early 2014 and judging by github, that milestone is 94% ready.
What is our best bet in this case when choosing Yii version? If we go with stable Yii 1, is it going to be easy to later update that code to Yii 2.0 or is it going to be a complete rewrite or some bad hack? Or if we go with Yii 2.0 alpha, will it be relatively easy to update then? The instability of alpha is ok, we anyway will likely be working on basic things such as authentication, registration, etc by the time beta is released? And finally is using the latest github commit (which is a 94% complete beta) a good idea or is it in a semi-functional "development" state and might not work at all?
Also how compatible are the Yii extensions? If we go with Yii 2, are we going to be limited to a relatively small selection of Yii 2 extensions?
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I'm using composer (in Symfony2 projects) and often get errors updating libraries.
Many libraries (most to my experience) use dev-master as version for their dependencies (or worse they use * ).
Whenever something is committed to the master branch you get to update the library, and the chances of an API change are higher as time goes by. What today in master is version 1.2.1 tomorrow could be 1.2.7, with no harm, and become later 1.7 or 2.x with sure incompatibilities.
My questions are
how did we get to this point? Is it a practice suggested from high profile sources?
what can I/we do to sensibilize the authors to this subject?
or
am I mad?
You are not mad.
It's a chicken and egg issue, until people tag more, others can not require tagged releases.
Nag everyone that has no tag or did not tag anything in six months (if the project is actively developed that is). I made an effort to tag all our bundles earlier this week, because I read a similar rant and I got reminded we still had only dev-master versions on most of them.
The solution really is education, and I will try to help a bit by pushing for best practices in composer docs. Not everyone has much experience with package management and many people don't realize how problematic this approach can be (until it's too late), so it's everyone's job to help by reminding them.