now Symfony2 PR4 is released, probably the last one before the official release.
I already have done some tutorials with the latest symfony 1.4 (the complete jobeet tutorial).
My question now: is it better to learn symfony2 before getting closer with 1.4?
if yes, any good sources for learning symfony2? blogs, books, etc..
thanks!
a big part of your answer should be based on your timetable. if you have to launch your project within the next 3-4 months then I would go with symfony 1.4.
since the GA release of symfony2 is not planned until early next year it would not be good to begin alot of work on that system since things may change and you may have bugs from the code that would be hard to track down.
even though there will be major changes between 1.4 & 2, I don't believe it would be wasted time learning 1.4
for learning symfony2, i would say the two best places would be the symfony site. blog here and forum here
Related
I've a slimframework v3 application that provide REST API for an Angular application.
I want to upgrade to v4, but there's quite a lot of changes and the upgrade page, while it mention what is changing, it's pretty dry on how to make those change and get a working application at the end.
For example, it says the new App() no longer takes the settings... ok... where does the settings go now ? Likely in the Dependency Container but this is changing too.
I fear that I will do a lot of code change and get a non working app and will spend ages on figuring out what's wrong.
So do you have any suggestion on how to proceed, step by step, to achieve a working upgrade from 3 to 4?
I've googled a bit, but I didn't find some walkthrough/tutorial on this subject.
I've managed to perform the upgrade.
It's way too long to document it here, so I've made a blog post here :
https://blog.mansonthomas.com/2019/11/upgrade-slimframework-v3-to-v4-how-i.html
I'll improve the article (readability & content)
Is Kohana framework alive or not?
Development site returns an error when I try to enter it. I can't seem to find Kohana in more or less modern PHP frameworks comparison tables (like this Wikipedia article)
I would consider it dead, but there seem to be some life signs in Github repo.
Than again, looking at their repo creates more questions than answers. Official site states that last stable version is 3.3.3.1, but last commit to 3.4 happened at January and last commit to unstable 4.0 core happened two years ago.
Were there some official announcements or releases I've missed somehow?
For all intents and purposes it's dead. There's a very small community that still uses it and makes some commits to the repo, but the staff abandoned it a year ago.
The official announcement was in the forum, you can read it here - http://forum.kohanaframework.org/discussion/12509/final-releases-of-kohana-beginning-of-ohanzee
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
I'm just starting on a software as a service project using CakePHP. I can see that version 3 is still in beta and I can see this project taking 3-6 months.
My question is should I start with version 2 or version 3 beta with the latter probably reaching a stable release.
I don't want to learn version 2 and then version 3 has a fair few changes.
Update: Go for CakePHP 3.0 now if you start a new project. CakePHP 3 is no longer in RC or beta state so it can be used without any doubts now.
The question is likely to get closed because it is opinionated, I'm undecided to put up a close vote for that reason myself, however...
Cake3 is in fact OK to be used for a project that is going to take 3-6 month - that is my opinion. But you'll have to expect a few API changes until then. I would not sacrifice the more modern architecture of Cake3 and language features, mostly the namespaces and closures for using an old version that doesn't support them just because Cake3 has not yet reached 3.0 (without the RC).
I've started using Cake myself when 1.3 was in alpha and the transition from 1.2 to 1.3 was pretty smooth. I've had to adept to the API changes during the ongoing development of 1.3 but this was not a game breaker and I never had to spend much time for it.
Same story with Cake3. We are using 2.x and started a new project using Cake3 and don't have much trouble with it. So far it just works fine and the occasional adoptions to the API changes are no game breaker as it was before.
You can see that Cake3 is mostly feature complete by now.
https://github.com/cakephp/cakephp/wiki/3.0-Roadmap
If you go further you'll notice that 3.1 is going to raise the minimum php version to 5.5.
https://github.com/cakephp/cakephp/wiki/3.1-Roadmap
This is because 5.4 is going to reach it's end of support. So there is no reason to support it any more. Based on this you can make your guess when 3.0 will be released: Likely before 5.4 is officially deprecated.
The one and only disadvantage of Cake3 right now might be the availability of plugins. But there are already lots of plugins that are upgraded to 3.0 and even new plugins for 3.0.
Update:
Absolutely 100% go with CakePHP 3.x. There should no longer be any debate as Cake 3 is now up and running and no longer in beta or RC...etc.
Original Answer:
If you're starting now (Jan '15), I see no point in learning CakePHP 2.x. Why go through the trouble, when by the time your project is complete, you'll already have out-of-date code (I know "out-of-date" might be a bit extreme, but...).
Not only that, but CakePHP2 and CakePHP3 are worlds different with a fairly sizable learning curve. I cannot imagine, at this point learning one language only to have to re-learn the entire thing in less than a year.
IF CakePHP 3 RC wasn't a viable choice (ie projects crashed all the time, or had issues left and right), and you're on a deadline, then you'd have no choice anyway. But CakePHP 3 RC seems to be running fine and is already being used on live projects.
The no-brain answer IMO: Go with CakePHP 3. I certainly would if I were in your shoes.
At this point (19th Jan 2014) , it is safe to go with cakephp 2 . cakephp 3 is not a stable release and there is no clear schedule date for stable release yet. I dont think it will be a breeze to update it later to a stable version if you develop in its current version . You might end up changing lot of code.
Hi I am working with cakephp since 1 year and I found that you can use cakephp 2.x because it is stable version don't need to extra configuration but in cakphp 3 is unstable version you install the composer in cakephp 3 & the structure of cakephp 3 is totally different form cakephp2 such as cakephp2 root folder is APP but cakphp 3 there is no app folder its contains src, bin, vendor etc
I found too many problems width cakephp 3.1 :
In appController, the function beforeFilter() is not working well as it was in cakephp 2.x, when I tape return false It should return a blank page but now It returns everything like if this function beforeFilter() in the appController is not controling nothing.
In Model, the functions beforeFilter(), beforeSave() and beforeDelete() have been replaced with too many functions in cakephp 3.1 but in reality those functions are not realy usefull, for the simple reason these functions don't work as we expected them to work, there is no centralization of these functions, you can say those new functions are not working at all.
The system of prefix and how we can contrôl access to some users to access to Admin/ prefix for example only from the controller and all the liberty this great functions of cakephp 2.x can give us now all this is gone with cakephp 3.1 and there are some bad restrictions you should respect.
cakephp 3.1 error managing are not helping you at all to found the source of the problem, it's like you're working with no compiler you found the source of the problem yourself, an if it's an very big project I garenty for you that you can failed at 60%....
too many reasons push you to wait for an other stable version of cakephp 3.x to start using this technologie.
I am a newbie in PHP Frameworks and would like to share/discuss some experience with you guys. Getting straight to the point, what I understand till now (from a newby stand of point is this):
CodeIgniter + Doctrine + Twigg = Symfony:
Zend + Doctrine + Twigg = Symfony
Symfony 2, uses php5.3 (I realy like namespace stuff remind me .Net)
but it lucks of tutorials right now (only partial jobeet translation to ver2)
I enjoy CI community and noumerous tutorials, plus using Doctrine + Twigg I could achive the same with Symfony.
Zend is more enterprise with lots of tutorials, but more difficult to grasp than CI.
So the question is should I start with CI + Doctrine or learn directly Symfony2?
Am I correct with the above assumptions?
Start with CodeIgniter if you are new to frameworks. Both Symfony and ZF have a greater learning curve and if you're not familiar with some concepts you might get fustrated in the beginning with the more complex frameworks .
I would suggest you to go with Symfony 2 since it has got lots of good stuff built around it. Take a look at this article http://www.phparch.com/2010/02/symfony-2-benchmarks/.
Hope this link is very useful on learning Symfony 2. It's a tutorials based on days (21) teaching you how to create a calendar website. Good luck.
http://symfony.com/blog/do-you-know-jobeet
More:
http://symfony2easy.blogspot.com/
http://www.dobervich.com/2011/03/03/symfony2-blog-application-tutorial-part-i-project-setup/, http://www.dobervich.com/2011/03/05/symfony2-blog-application-tutorial-part-ii-the-data-model/, http://www.dobervich.com/2011/03/09/symfony2-blog-application-tutorial-part-iii-routing-controllers-and-templates/
it really adds up to what your requirements are.
Symfony is great, though my only bash on it is that it requires PHP 5.3, which is great, but make sure your host has 5.3 support. Also the issue of using CLI bugs me.
CodeIgniter 2 on the other hand requires 5.1.6, which is good for me as my host is still on 5.2; I also like how small CI was compared to Zend or Symfony. Now like you i like some of symfony's components and i use 2 of them (swift mailer & twig) on my CI install. doesnt mean you should just junk ci and go symfony. CI is built to be a stepping stone framework that you can build on. Symfony to me is a full-fledged framework with everything and the kitchen sink.
having said all that, not all frameworks are created equal. I use CI for one project and Kohana for another. Kohana offered me something i liked that CI didnt do and thats fine.
I think you should look at the different frameworks out there, some are full featured, some are bare-bones and allow you to grow with your needs.
You may quick start with Cygnite PHP Framework. Simple yet powerful tool to build your next project. It gives you exceptional performance. Check benchmark results:
Performance benchmark results
Just giving Symfony a test-drive, and I'm really falling for Netbeans. Seems like a good combo, although I'm a rookie with both.
According to some tutorials and informational webpages (like this one), Symfony 1.x has a "symfony" script which, among other things, Netbeans uses to automatically generate Symfony projects, including front- and back-ends.
Does Symfony2 have the same capability, or will it after it reaches gold master? Otherwise, what strategies are there for integrating Symfony2 with Netbeans?
I don't think so. Maybe in a future release of netbeans. Symfony2 is too young.
edit 16 december 2011 :
netbeans symfony2 support has started :
http://blogs.oracle.com/netbeansphp/entry/initial_support_for_symfony2