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.
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 6 years ago.
Improve this question
I originally asked a biased question about which MVC framework is best suited for high traffic.
The answer to this question is that most frameworks can are designed handle such traffic. Choose the best MVC framework you are comfortable with.
Donald Ervin Knuth:
Premature optimization is the root of all evil (or at least most of
it) in programming.
Most of the tools we're using (including frameworks in general and Laravel in particular) are designed to speed up development process and then ease developers workflow.
The general rule here I'd say is build it first. By the moment your project becomes so big (read successful) that Laravel on PHP7 fails to deliver you certainly will be able to hire someone to tackle that problem.
Therefoe Laravel is a decent choice for a new project, like any other framework.
Ideally write your application logic in a framework-agnostic manner, i.e. keep Laravel out of your business logic - that requires some experience, but in the end you would even be able to switch frameworks.
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 6 years ago.
Improve this question
I have started a project to convert some parts of laravel framework to compiled php extensions to improve the performance. I have created a git repository for the migrated parts and another for the laravel modification that will use that extension.
My question is how to build completly all laravel from framework kernel modified?
Do you think that I'm doing well?
I have started a project to convert some parts of laravel framework to
compiled php extensions to improve the performance
...
My question is how to build completly all laravel from framework kernel modified?
Just don't. Laravel is a framework that is changing quite frequently and your attempts to make it working as native code will fail, because every composer update command call will force you to rebuild native implementation.
If you want to put heavy effort for performance optimisation, then go for other frameworks as Falcon, or use Lumen as an alternative (it's lightweight version of Laravel). That's all I can tell about Laravel itself, because optimisation have not only place in Laravel kernel, but also in database design, scale of the project, and other network configuration settings.
Provide more specific information about bottlenecks in your project, and you will get answers that you are looking for.
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 am wondering whether I can use PHP frameworks such as Symfony2 or Laravel with a CMS like Joomla. I have worked with PHP, but a beginner of Joomla. I know I can use extensions like Sourcerer. But I would like to use Laravel of Symfony2 instead. For example if I am developing a website where there is a considerable amount of server-side programming and also a lot of web pages to display, could I use Joomla to handle the content management and a PHP framework for the server-side programming?
In brief my question is :
Is there any way to integrate a PHP framework(preferably Laravel or Symfony) into a website built on Joomla! ?
If it is not capable of doing, what are the other options available; or is it not recommended to use PHP frameworks along with Joomla?
It would be possible, to integrate your framework into a CMS - so your managers or reporters or whatever, can change content. But that would be horrible amount of work. Better use Content management systems on their own.
It is possible to use Symfony2 with the CMS RedKite. An "Extension - CMS" for it.
More information under:
http://redkite-labs.com/
It's not possible. Joomla is build with its own framework and API.
As of Laravel you could give https://github.com/FrozenNode/Laravel-Administrator a try. It's a sweet CMS for your own models. I love this, since it's not restricting your coding and you can work with your back-end code.
If you're looking for a more client-friendly solution, http://octobercms.com/ is in the works and should hopefully be released soon.
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 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.