Does application build on Laravel 3 work on Laravel 4?
In few days ago I found Laravel and now I try to learn it. Am I losing time learning Laravel 3 when Laravel 4 is coming? Is this a same with some addons in LV4? And would my application build in LV3 work in LV4?
Where and how to start learning LV4?
Laravel 4 is currently in beta 1 with beta 2 coming this or probably next week. To answer your question directly: yes your Laravel 3 (L3) application will break in Laravel 4 (L4) because L4 differs in quite a few points from L3. But L4 was designed with migrating from L3 installs in mind so you definitely don't have to rewrite your entire application. You probably only need to update some routes, functions and implement some new ways L4 handles certain key aspects. Like others stated here, a migration guide isn't available yet but you can bet that when L4 gets released a lot of tutorials and guides will be made available.
You're not losing time learning L3 since much of L4 is still the same as L3.
The docs of L4 will help you transfer from L3 to L4. Taylor said (and I agree) that you shouldn't wait until L4 gets finished. If you want to build an app and release it for production soon just go with L3 and migrate later on.
The way L4 implements bundles differs from L3. L4 uses composer to install dependencies into the framework. You can always still use bundles directly in the app but they probably need to be updated to work along nicely with the updates in L4.
To start learning L4 the documentation is a great way to do so. You won't learn everything but work isn't done on the docs either. There's more to come as more betas get released.
If you want to learn more about L4 here are a few nice tutorials to get you started:
What to expect from Laravel 4 by nettuts.com
Laravel 4 tutorials by Jason Lewis
There's much more out there but this should get you started :)
This should hopefully answer all of your questions: http://four.laravel.com/
I haven't seen a migration guide yet, but then I haven't looked too hard. I'm sure if there isn't one yet, there will be soon
Related
I've begun using Laravel 5.4 instead of Spring boot for a web application I'm currently developing and it's going great. I'm really enjoying the lack of verbose boilerplate that Java/Spring has. However, one of my requirements is that the API must be HATEOAS.
I've literally searched for days for research material and only come up with a couple of not-so-popular libraries. Is there a reason for this complete lack of exposure of HATEOAS for Laravel when for other web application frameworks there's at least some material?
Edit: I'm not trying to talk down on Laravel, I just want to know why there's no resource on HATEOAS implementations with Laravel as the framework, or if I've missed it, where I can read up on some HATEOAS Laravel goodness.
Since Laravel uses the Symfony underneath, I think this repo would work: https://github.com/willdurand/Hateoas
This may silly question. But I am going to start new project. I am quite confused which framework is best out of Codegniter 3 and Laravel 5.
What is the main difference between them.
Thanks in Advance
Right now, I personally prefer Laravel since it supports PHP7 unlike CodeIgniter (I still haven't read if CodeIgniter 3 supports PHP7). And based on personal experience, Laravel (through Eloquent) has "beautifully-written-codes".
Here are some references for you to check out: (I made sure to post both sides to not be bias)
https://www.codeclouds.com/blog/laravel-vs-codeigniter-a-difficult-choice/
https://www.clickittech.com/developer/laravel-vs-codeigniter-which-one-is-the-best-to-use
http://www.codeigniterhands.com/codeigniter-or-laravel
http://laravel.io/forum/07-08-2014-laravel-vs-codeigniter-a-difficult-choice
https://therightsw.com/codeigniter-vs-laravel-vs-yii-vs-cakephp/ (with grades for usability)
Each framework have their own features and capabilities, used during the development of application. Laravel is one of the highly used, open-source modern web application framework that designs customized web applications quickly and easily.Laravel is used not only for big project but also best to use for small project.
Best framework in 2018
If you want a framework with exceptional performance, with nearly no configuration, not using cmd and not interested with large scale libraries and also your project is in small scale it's better to use codeIgniter.
CodeIgniter3 vs Laravel5
Both framework are good in there place.
Laravel made from multiple open source project which make laravel more efficient , reliable and secure.
Where, laravel used blade engine.
It used composer for package manager.
It provide unit testing.
It provide more security.
It provide beautiful redis queue front portal called laravel horizon.
Disadvantage : laravel used predis which is slower, because it is written in php.where phpredis is more faster, but laravel 5.* Don't support it.
I will recommend you to use Laravel beacuse of:
Built in authentication
Awesome migrations
Artisan commands to do anything in your project
Built in pagination (It's took long in Codeigniter)
Eloquent (Very easy way to interact with your database)
Relationships
Routes
Easy API building
Easy debugging
Huge number of packages and libraries etc.
I made a website and I spend about 2 month on it, I made it by Laravel 4.2 and now I see the new version of Laravel released (Version 5).
My Questions:
Should I change and work with Laravel 5?
What happens if I don't change to Laravel 5? Does Laravel 4.2 Works or it has security issue?
Why does Taylor change the coding style of Laravel? (I know Laravel 4 had lot of diffrent with Laravel 3, And this is not good for Developers.)
Edit:
I learned Laravel in about 2 weeks, How much time do I need to learn or migrate to Laravel 5?
To answer question 2 - Laravel 4 will continue to work. Taylor provides back-ports for security issues - so it will continue to remain a viable framework.
In saying that - the upgrade guide from 4.2 to 5.0 shows you how to upgrade. Most websites can be upgraded in less than 4 hours (from reading various forum posts) - so you could just upgrade and take advantage of the many awesome new features.
Regarding your first and third question, you have to deside for yourself.
That being said, in order to make a fact-based judgement, I would advise you this:
Check out the free Laracasts serie introducing you to Laravel 5
Listen to the Laravel podcast episodes 18-21 where Taylor Explains new features and why he changes things like the file structure
Read the release notes (as The Shift Exchange noted) to find out new and useful functionality in Laravel 5
No need, the difference between Laravel 4 and 5 is mainly structurally, both depend on third party libraries via composer.
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.
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