Live data from Hacker News

Laravel 5 released

laravel-news.com

91–100 of 114 posts

Re: Laravel 5 released

#92

Earlier quoted context omitted.

Maybe 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.

I don't see how Laravel lends itself to "rapid prototyping" than any other framework. Sure, Symfony2 or ZF2 has best practices on how to do things, but at the end of the day it's just MVC - you can skip any best practice you want to just get something done. This isn't unique to Laravel.

It's less verbose than Symfony2 and, being pretty opinionated, requires much less configuration for new applications.

Facades, macros and route closures supports rapid prototyping and are pretty easy to replace as needed. Included libraries like Flysystem, Cashier, Elixir and the new cron wrapper also eases rapid development.

There are also a few tools around it, like Homestead and Forge, that makes it easy to set something up quickly.

It's not like you can't do rapid prototyping with other frameworks, but Laravel, to me, is the first PHP framework that actively supports it while providing a flexible enough structure to grow in.

Re: Laravel 5 released

#93
post #22
post #15

Earlier quoted context omitted.

No, they also suffer from the pattern misuse pattern and are also slow as hell.

It would benefit the whole community if you documented your complaints (and suggestions for improvements) in a blog post we can all read & comment on.

[deleted]

Re: Laravel 5 released

#94
post #22
post #15

Earlier quoted context omitted.

No, they also suffer from the pattern misuse pattern and are also slow as hell.

It would benefit the whole community if you documented your complaints (and suggestions for improvements) in a blog post we can all read & comment on.

[deleted]

Re: Laravel 5 released

#95

Earlier quoted context omitted.

Did you just go full retard?

Is that supposed to be funny? Maybe he went all "autistic" too? Perhaps he types like a "Jerry's kid"? Grow up, and behave like an adult who actually takes care in choosing their words.

> Full Retard, also known as Nigga, You Just Went Full Reatrd, is a catchphrase associated to Kirk Lazarus, a character from the 2008 film Tropic Thunder portrayed by Robert Downey, Jr. The expression is normally used as a reply to ilogical or stupid posts, in similar fashion to other phrases like Facepalm or What is this I don’t even

Get the stick out of your ass.

Re: Laravel 5 released

#96
post #88

Deal-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…

Those 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.

Yeah, 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.

Re: Laravel 5 released

#97
post #64

Earlier quoted context omitted.

Extending the IoC container?? A ControllerFactory?? You never do anything like that in Symfony. The thing I appreciate most about Symfony2 is how it enforces good design patterns.

One might argue that the SOLID principles applied in Symphony and inherited by Laravel are in fact anti-patterns which only serve to add massive cognitive overhead. They've wrecked countless Java projects over the years and are now going to do PHP the same favor. There's even less reason for a scripting language with a GIL to be saddled with this level of complexity, than there is for Java.

Can you elaborate on "the SOLID principles [...] are in fact anti-patterns"? I don't see this point of view exposed often, can you point me to some resources in this regard?

Re: Laravel 5 released

#98

Earlier quoted context omitted.

I don't see how Laravel lends itself to "rapid prototyping" than any other framework. Sure, Symfony2 or ZF2 has best practices on how to do things, but at the end of the day it's just MVC - you can skip any best practice you want to just get something done. This isn't unique to Laravel.

I think it tends to do with the marketing. Lots of hand-holding walk-through tutorials and help people get "rapid" prototyping with laravel, moreso than the actual code itself. And, to an extent, when you present yourself as being good for "rapid dev", that's what people will associate with the framework. (by comparison, zf has never promoted itself as allowing for rapid development, AFAIK).

> by comparison, zf has never promoted itself as allowing for rapid development, AFAIK

Well, no, because everyone would laugh at them.

Re: Laravel 5 released

#99

Earlier quoted context omitted.

It strikes me as a project that should've been an internal framework, not a public one. Too many things break and change constantly. Rapid release cycles is a good thing for smaller libraries with specific tasks, but I expect a framework to remain largely unchanged (except bugfixes, of course) for longer periods of time. Unless Taylor gives away control of the project, I don't see it happening. It'll keep being a pop…

As a Core developer of CakePHP, I'll tell you that the community at large loves major releases more than they like stability. Something about using the newest toy really gets a lot of people going. We actually have had quite a few developers tell us our framework is dead, despite ongoing development on a new major release and monthly minor/patch releases for the current stable line for 3+ years. I can't comment on La…

The vocal community is likely in the realm of 5-10% of the actual active userbase. You should cater to most of your users, not just the bored ones.

Your framework is dead because you've continued to prove that you don't understand what PHP 5.3+ is and means. I say that as someone who has been forced to use CakePHP for ~10 years. You've always lagged far behind in the concepts that other frameworks have down pat.

Re: Laravel 5 released

#100

Earlier quoted context omitted.

I am going to have to completely disagree with you. I have been using it for several years now and I have nothing but good things to say about it. The ORM is basic yes, but that's the purpose of it. If you want a bigger one do what you do with Symfony and use Doctrine or something more robust.

I just tried to two days ago and did a complete project with it. Auth, CRUD, file management, etc. It's an instant love for me. Docs is mostly ok, Google provides instant answers. I'm happy to ditch CodeIgniter for this.

I spent two days just trying to get the thing installed and gave up. Kept hitting a snag somewhere. Such a bummer because I was excited about using it.
Post reply on HN