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 9 years ago.
Improve this question
I wonder if Symfony 2.0 is stable enough to use?
Because I've never used Symfony before.
It seems that Symfony 2 is much better than the previous version and I don't want to relearn/recode everything some months from now.
When do you think it will be released?
Would it be a wise choice to use 2.0 now?
No.
Yes. http://symfony.com/download
http://symfony-reloaded.org/learn
Quote from above link:
Please note that Symfony 2 is not yet ready for production. The final release is planned for late 2010 and will only support PHP 5.3.2. In the meantime, we highly encourage you to use the current symfony 1.4 stable release for all your projects.
Symfony core team member here. No, Symfony2's not ready at all to be used in production, because it hasn't even reached the alpha state. As stated on the github page, things (especially the API) WILL change.
Furthermore, some components are not here yet, for example the Forms framework, so you would have to handle them by hand. Don't do that. But of course we'd be more than happy to get some feedback if you give it a try for a sandbox project of yours ;)
I would like to point out that we (www.exercise.com) are live and have been using Symfony 2 for a while now.
It has not been the most smooth experience (we try to stay up to date with the most recent sf2 branches on git, which is almost a full-time job for 1 person), but we have built a functioning site.
The largest hurdle right now to starting a project is the lack of documentation and examples online. So while it is possible to run a production site using Symfony 2, the framework still has a long ways to go until it can be used for a small project.
Yesterday at SymfonyLive 2011 (Twitter #sflive2011) Fabien said that the first Release Candidate will be March 2011.
Related
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
How time consuming is migrating a medium/large sized legacy Symfony application from version 2.3 to 4.4 compared to rewriting it in a different framework?
From the research I've done it seems like quite a lot of stuff has changed between these versions so I'm trying to weigh this decision up against just rewriting the whole thing in Laravel (the framework I'm experienced in). I'm trying not to get stuck in a wormhole of rewriting abandoned code.
The main reason for the upgrade is security fixes, running Symfony 2.3 in 2021 doesn't seem like the best idea to me. The codebase won't need any changes in the near future.
Following is an overview of used packages.
Upgading you symfony version that much means 3 steps:
upgrading your php version (PHP 5.3.3 to 7.1.3)
upgrading your package (most of them will not work any more or have lot of changes)
upgrading symfony
It mostly depends of your code coverage: if you have a good code coverage, you will be able to quickly identify remainings bug
otherwise it depends on your legacy:
are best practice used?
is the code clear?
is the code well decomposed?
For larger project, i don't recommand to create a new one: it cost a lot of money and may prouce bugs and regression
The best way to do it is step by step. Determine which package to upgrade one by one, do it and push it in production with the apropriate code coverage.
Start with your php version: on local, have your devellopement be run in higher php version to identify most bugs and correct them
Manage each of your abandonned project to replace them with the recommended one
we had to deal with phpexcel to php spreadsheet. We identify each place where it was used in the application, and update each of them, one by one (having both package on project). When phpexcel wasn't used anymore, we deleted it
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
First of all I should remind you I have read some links and done some research and looked at some old questions but I still have a question.
I want to start a project with codeigniter 3 but I have heard that codeigniter is not secure enough!
I don't know if it is correct or not, so I started researching about it but now I still don't know. Should I start my project with codeigniter or not! I don't know how to work with any other frameworks and I don't have enough time so I want to ask you if I should start my project by codeigniter. Is it really unsafe? and what shall I do to make it secure or is it possible or not?
I know that the security depends on programmer but I want to be sure that codeigniter does not have a big security bug that any hacker can hack my project and destroy it.
what would you do ?
I'm really afraid
Codeigniter is a framework and is not solely responsible for your site's security. Your site's security is truely determined by the code you write with CodeIgniter. An empty CodeIgniter install is very, very secure. Simply because it's not using any user input or operating with any database.
Codeigniter 3 is no longer in beta and has a stable release available here: https://codeigniter.com/download
If your concern is security, make sure you develop the site with security best practices. Typically, if a site is hacked, it's due to a lazy developer and not the framework they were developing with.
along with security are all the million other things that can go wrong on the server or "cloud" which is hosting your application. so -- even if its just you working on the app -- become comfortable with git and version control. i just discovered the phpstorm application for developing php code and it has version control built in, along with other features that makes it easier to maintain more then one working copy of your application.
otherwise to your question - Codeigniter is being actively maintained, has a friendly community, and the code is very fast & stable in production.
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.
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
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.