10 ms·
Laravel 5 released
- emilsundberg 12y agoMore info: http://laravel.com http://laravel.com
- ponyous 12y agoI love the `Architecture Foundations` section in documentation [1]. I wonder why more frameworks don't do this. It happens a lot that I have no idea where to put files when I start with some frameworks. I am still not sure how good it is but I am reading through it right now. [1] http://laravel.com/docs/master/providers http://laravel.com/docs/master/providers
- vruiz 12y agoLooks like some links are broken. For example http://laravel.com/docs/authentication http://laravel.com/docs/authentication redirects to -> http://laravel.com/docs/4.2/authentication http://laravel.com/docs/4.2/authentication which is 404.
- jbrooksuk 12y agoSeems to be working fine here. Try again?
- smacktoward 12y agoIt wouldn't be the first time. When Laravel 4 came out, they decided the best way to announce that would be to make all the old URLs for Laravel 3 documentation point to Laravel 4 pages, and then take down the Laravel 3 documentation completely. Yes. Completely. Not just "put it in a less prominent place" or "hide it six levels deep in the directory hierarchy" -- it was gone, overnight. Poof! Vanished. I happened to be in the middle of a Laravel 3 project at the time, so the sudden removal of all documentation for the version I was working with was more than a little painful.
- colinramsay 12y agoThere's an article specifically about the release here: https://laravel-news.com/2015/02/laravel-5-released/ https://laravel-news.com/2015/02/laravel-5-released/ It might be a better way to get an overview of this release as it links to various other articles about v5. An article specifically on the changes: https://laravel-news.com/2015/01/laravel-5/ https://laravel-news.com/2015/01/laravel-5/
- Scarbutt 12y agoCan you really write beautiful code in PHP?
- coldtea 12y agoSure. PHP, especially post 5.4 has matured a lot and offers as many niceties as your favorite blub language. It has its warts, but at this point, nothing worse than what Javascript has for example. That said, while you can write beautiful code in PHP, IMHO, Laravel is not that. It full of "string typing", over-applied and mis-applied Design Patterns, and poorly thought abstractions. It just saddens me that Laravel is considered well designed and advanced codebase, or, worse, a standard of how PHP should be coded. While it's not as bad as the Wordpress spaghetti, it is mostly Java EE (circa 2004) in PHP, sans the strong typing assurances (and, fortunately, sans the gobs of XML too). On the other hand, Laravel works and has a strong community going for it, which, as in the case of Wordpress, makes all the difference in the world.
- xoe26 12y agoCan you give an example of a well designed PHP codebase? Are any of the other frameworks (Symfony2, Zend, etc..) better?
- snomad 12y agoNot a framework per se, but several independent packages, http://thephpleague.com/ http://thephpleague.com/ has some well written and nice code.
- dscrd 12y agoNo, they also suffer from the pattern misuse pattern and are also slow as hell.
- bojanz 12y agoIt would benefit the whole community if you documented your complaints (and suggestions for improvements) in a blog post we can all read & comment on.
- graystevens 12y agoFor those currently using Laravel, here are some upgrade guides due to the large changes from 4 -> 5 http://laravel.com/docs/master/upgrade http://laravel.com/docs/master/upgrade http://mattstauffer.co/blog/upgrading-from-laravel-4-to-laravel-5 http://mattstauffer.co/blog/upgrading-from-laravel-4-to-lara...
- T3RMINATED 12y agotaylor i love you
- saluki 12y agoIf you're new to Laravel or want to learn more check out http://Laracasts.com http://Laracasts.com. Jeff Way does a great job. (Just a fan/current subscriber).
- lukeholder 12y agoI agree, awesome resource which is rapidly levelling up many modern php developers.
- Matachines 12y agoJeffrey Way is the best. Back at Tuts+ I'd only watch his courses—no one else was as good of a teacher as him. Laracasts is even better.
- cozuya 12y agoHis 30 days to learn jQuery was a critical growing tool for me - if you're at all interested in low-level front end JS, definitely check it out. Its free.
- Matachines 12y agoThat's actually the first course I took by him. I took a few of his other HTML/CSS courses and I am doing PHP Fundamentals (to get into Laravel later) because of the "jQuery and PHP" parts of the 30 days course. All good stuff.
- pwenzel 12y agoAgreed. Definitely worth paying for.
- brianbreslin 12y agoWhat are the main advantages of Laravel over say Cake or Symfony?
- BaconJuice 12y agoLet's add Codeigniter to the list too. Need a pitch for the employer.
- brianbreslin 12y agoI thought codeigniter was dead? I could have sworn they announced 2 years ago it was no longer going to be developed.
- SBullet01 12y agoThe framework found a new home and its now under active development again. Unfortunately, since v3 which is still not officially out, the framework has fallen behind its competitors.
- rooodini 12y agono longer developed by EllisLab, perhaps.. https://github.com/bcit-ci/CodeIgniter https://github.com/bcit-ci/CodeIgniter
- mediascreen 12y agoIt was revived a while ago: http://forum.codeigniter.com/thread-650.html http://forum.codeigniter.com/thread-650.html
- WA 12y agoI just started with Laravel and can't compare it really well to the other frameworks, but this is what I like so far: - it's well-documented - it has an active community - I simply enjoy working with it. It feels lightweight, although it probably isn't, if I take a good look at the "vendor" folder and the dependencies - I get stuff done relatively quickly Edit: So I started porting my small Laravel 4 project to 5 and to be honest, my first impression is: Laravel 5 is more like Zend Framework than the small and nice PHP framework. It lost a bit of its lightweight flair for a potentially more structured architecture, but I kind of hate to put everything in "Service Providers" and "Middleware" and whatnot. E. g. before, you had a folder "app/controllers", now you have "app/Http/Controllers" and "app/Http/Middleware" and "app/Http/Requests". While this might make sense for bigger projects, it also loses a bit of its lightweight charm. With Laravel 4, things seemed to be more straight forward.
- dieg0 12y agoAwesome news, been expecting this since a mysterious twit last week, Laravel is awesome, can't wait to check v5 thanks!
- gude 12y agoLaracasts has a series of introductory screencasts on Laravel 5: https://laracasts.com/series/laravel-5-fundamentals https://laracasts.com/series/laravel-5-fundamentals
- lukeholder 12y agoLaravel represents what modern PHP can do and be. Clean, organised, fully object-oriented. Kudos to what Taylor Otwell has created both from a marketing perspective and technical standpoint.
- deweller 12y agoI was a little scared by the heavy use of static method calls in Laravel 4. L5 has made the statics easier to ignore if that is not your thing. But after understanding the Facade pattern that is widely used by the framework, I've concluded that the use of the static method calls is not an antipattern at all.
- raziel2p 12y agoIt really is less of an antipattern in PHP than other languages. With every request being its own process you don't have to worry about singletons as much, and as long as it's easy to swap with mocks/fakes/whatever it's all good.
- coldtea 12y ago>Laravel represents what modern PHP can do and be. Clean, organised, fully object-oriented. In a JavaEE circa 2003-5 way. Not exactly what modern programming is about...
- cbg0 12y agoWe got it the first time https://news.ycombinator.com/item?id=8997114 https://news.ycombinator.com/item?id=8997114
- coldtea 12y agoDifferent subthread, answering to another person. Besides, it's not like https://news.ycombinator.com/item?id=8656965 https://news.ycombinator.com/item?id=8656965 is some gem of a comment that hasn't been written 200 other times on HN for example.
- 12y ago
- leftnode 12y agoI'm a fan of Symfony but love that there are several advanced frameworks pushing the state of the art forward (Symfony, Laravel, ZF2).
- whatsthatyousay 12y agoIve been so excited about this! Though I kinda miss the call to action buttons that they had on the old site. Scrolled down the page looking for the quickstart button before I had a "duh" moment and clicked on documentation.
- rdoherty 12y agoAfter using Laravel 4 for an internal company tool I have a hard time recommending it (sadly, I was hopeful). I found the docs to be uneven in quality/scope, some key features (mostly around the ORM) missing and the 'feel' to be slightly off. It's hard to quantify, but I have used CakePHP, Yii, Rails (0.9 through 4), Django and plenty of home-grown 'frameworks'. From all those the most cohesive and understandable to me was Rails followed by Yii (surprisingly). Maybe it's the docs or structure, but Rails and Yii have a strong opinion and it seems their developers have both CS smarts and industry experience, which shows in the structure and code. I'm sure in time Laravel will mature and improve. Currently it just feels like there's a lot more hype than it merits.
- mediascreen 12y agoMaybe it's a matter of taste? I have worked with Symfony2, Zend Framework, Yii, Kohana and Laravel and find Laravel the most intuitive to work with. I like that you can start using it for very rapid prototyping and refactor into more complicated structures as the application grows.
- gerardnll 12y agoTotally agree. I think that Symfony2 is a pain in the ass. Laravel lets you have something working really fast. Then you can improve the code later on.
- Ronsenshi 12y agoI concur. Symfony 2 is incredibly powerful, but at the same time incredibly messy to work with.
- wesray 12y agoAgreed, Symfony2 is great, but I see it being used more in an open source project capacity. Working on it at a company where time frames are key, rapid development is huge. Plus, laravel is far more intuitive and I can ramp up new team members much faster.
- 12y ago
- mcmillion 12y agoI tend to use Laravel when the client/project forces me to use PHP rather than Rails. It's not bad when coming from the Rails world. I also have a bit of pride that it's made in Arkansas. Yes, we have computers and the internet here.
- ianhawes 12y agoHaving watched Laravel 5 throughout development, I'm personally unhappy with the fact that most of the nice features of Laravel have been removed. For example, the default version of Laravel 4.x shipped with the "Whoops" PHP stack trace view, which is far superior to the L5-default Symfony stack trace view. Other features were removed too, including the HTML library. Blade tags were changed for no reason. Overall, it feels like instead of adding requested features, Taylor decided to redesign the architecture for no reason.
- raziel2p 12y agoThe single maintainer just didn't want to maintain them, which goes to show how Laravel really just is his personal project that got really popular, not a community-driven effort.
- ceejayoz 12y agoIMO, that fact has helped make Laravel successful. Sometimes, software projects benefit from a benevolent dictator rather than design-by-committee.
- fideloper 12y agoFUD. The "architecture" change is the bootstrap repository, which has a new folder structure. I know, scary stuff! Folders! The "architecture" has some enhancements to middleware and fleshing out events/commands to a "command bus". Basically, you get more sugar on top of the (mostly) same architecture. Whoops caused a lot of headaches behind the scenes, and did stupid things like convert ALL http error responses to 500, even on a 404 error (which showed up in Whoops, as HTTP errors are converted to exceptions within Symfony's HTTP stack). Blade tags have one new tag, and the old ones still works. This point might be the subjective one - HTML library. HTML libraries create an enormous amount of support for people's edge cases and generally are better pushed out as a third-party add on to suit your needs. The upgrade guide explains how you can add them back in if you want. https://github.com/illuminate/html https://github.com/illuminate/html
- 12y ago
- import 12y agoBad to see, Laravel still doesn't have an LTS version. Upgrading is a pain.
- ceejayoz 12y agoMight be a business opportunity, ala https://railslts.com/ https://railslts.com/.
- iN7h33nD 12y agoI really like Laravel, it makes getting things started easier. I am glad I finally have a good way to manage my assets from within Laravel so that I don't have to deal with all of that myself every time. The only thing I find Laravel lacking is Web Socket support and every time I tried to implement something I would basically give up and switch to Node.js. Is there anything that can get web sockets working in Laravel?
- debaserab2 12y agoDeal-breakers for me with Laravel: - Blade templating language. I don't need yet another templating syntax to learn, especially one that isn't analogous to others I know and are common among other frameworks. - I really can't imagine going back to an active record based ORM. I've learned too many hard performance lessons from Doctrine1 and rails at this point. - Facade/proxy pattern based classes. I think as they are implemented in the actual framework, these are done correctly. However, I think the userland understanding of this pattern is often lacking and leads to a lot of glorified singletons that are some how touted as acceptable because they call them facade/proxy based. In the giant lineup of frameworks, ranging from something as simple as SlimPHP or silex, all the way to enterprise targeted frameworks like Zend Framework 2, I just don't see why I'd ever pick Laravel as the go-to solution in any use case.
- JonoBB 12y agoThose don't have to be deal-breakers. - You don't have to use Blade. Use Twig or Smarty or whatever you want - You don't have to use Eloquent. Use raw queries or Doctrine or whatever you want - You don't have to use Facades - use the IOC container to get whatever you want Its so easy to plug-and-play with composer, and there are so many other features to laravel.
- debaserab2 12y agoYeah, at that point why use Laravel? All the major frameworks are just as decoupled, but as soon as you start selecting off the "native" defaults for things like templating and ORM you lose integration features that have been built into other areas of the framework to support that specific library.
- aikah 12y agowhat the point of it then? just use Silex,it's better,faster and simpler.
- vatotemking 12y agoi dont want to depend on a framework by one person.