laravel-vs-symfony/

[modess]

laravel-vs-symfony/

Laravel vs Symfony
https://modess.io/laravel-vs-symfony/

[modess]

Originally posted by Pablo Ezequiel Leone Signetti on 2014-04-24T15:36Z

---

I don't understand your point. Are you saying that Laravel is a symfony extension?

Laravel use a part of the symfony components, not all and the architecture is different, easier.

I prefer Laravel, and I think we can compare them because they are used for the same task and whether you know them or not, Laravel is easier to understand, better documented, and faster for development.

Nice post!

[modess]

Originally posted by gchokeen on 2014-07-15T11:25Z

---

Niklas Modess Great article !

When someone ask Symfony2 vs Laravel, I think it means they want to know which one is suitable for their web app. In my perspective Symfony2 is vast and it's suitable to develop big web system not just website. I never checked Laraval yet!

Let's just rephrase the question? I want to develop the web tool (Saas). I am worried about code standard, security, extendibility and so. Which one will you pick Symfony2 or Laravel and why?

[modess]

This is a fairly better question, but I'm still not very fond of it. Since Laravel is only a layer on top of Symfony2 (pretty much), where all the underlying components are easily accessible, you get the extendability of Symfony2. So if you can extend a component in Symfony2, you can do the same with it in Laravel.

Security and performance might be one thing, but both have extremely active developer communities and it will probably be hard to tell which one is doing it better. It will mostly come down to a matter of personal taste.

[modess]

Originally posted by turpana on 2014-08-07T02:11Z

---

So you prefer Lavarel, but what's that sugar on top that you refer to? I get that Lavarel is built with Symfony2 components, but I'm still interested as to why I might try Lavarel vs Symfony2 on its own. FWIW, I'm coming from the perspective of looking for a light php framework. I usually build with Drupal or Wordpress, but am looking to try something new for a project that doesn't require the CMS component.

[modess]

Originally posted by Dmitry Varennikov on 2014-12-03T00:53Z

---

> I'm not a fan of either YAML or annotations for routes. With YAML you can't use a closure for simple and fast routes. Personally I also use dummy routes a lot for debugging purposes.

You use the wrong tool for debugging purposes. And yes, mixing controllers with closures leads to a muddy code.

With annotations you do not have your routes gathered in one place, I like the idea of having them all in routes.php.

This looks convenient for you just because you put everything in one place. If you developed a huge application with more than one module you'd suddenly notice that not all of your routes are in one place, because they go along with a module they belong to. And then have routes in PHPdoc blocks in controllers is not a bad idea at all.

[modess]

When I need to do some minor debugging, I just use a route even though it's quick and dirty.

I have been a developer on a few huge applications. I still think that each module should have their routes gathered in one place in each module.

But again, it's what I find prefer and find convenient. Just like pretty much anything, it won't work in all cases.

[modess]

Originally posted by Dmitry Varennikov on 2014-12-03T22:45Z

---

How would you share your module if routes don't go along with it? How would you install 3d-party module without routes? Look at Symfony bundles and how they are packed.

Regarding debugging. Look at Symfony debug toolbar. It contains a lot of information (request, form data, template variables, db queries and other), it may intercept redirects, so you know what's going on after successful form submissions.

[modess]

You misunderstood me. I meant that each module can have their own routes in one place (file).

[modess]

Originally posted by Dmitry Varennikov on 2014-12-03T23:17Z

---

Well, routes in controller annotations is also a "one place". Controllers are API ends of an application, and information on how to reach them is located right in place.

[modess]

Originally posted by Teoh Han Hui on 2014-08-18T19:39Z

---

An apples-to-apples comparison should be between Laravel and the Symfony2 framework, not the Symfony components. The Symfony routes example in your comment is totally not how it's usually done.

I am a developer who's been working with (i.e. using) the Symfony2 framework for a year and a half now...

[modess]

I got that from the current Symfony2 documentation. Could you show how it's done in a correct way?

[modess]

Originally posted by Teoh Han Hui on 2014-08-19T15:02Z

---

http://symfony.com/doc/curr...

Oops... I just realized you referred to the PHP code snippets. I'd think most devs would go with YAML and annotations, much like how most devs would go with Twig templating instead of PHP templating (in the context of Symfony2 framework).

So it actually becomes just a matter of configuration (Symfony relies on convention in a lot of places, but not for specifying routes). No code required.

[modess]

See my other answer on YAML/annotations.

[modess]

Originally posted by Petar Zivkovic on 2014-09-24T20:18Z

---

Nice article, and I too am guilty of asking that question to my developer friends that use Laravel.

The reason I ask is because I've had some exposure to Symfony, but not Laravel (not since v2 at least); so I am genuinely interested in some of the differences in actually using one vs the other... what happens when you have to get your hands dirty and build an app! :D

I am often told that Laravel's learning curve is much easier to follow, and a lot of things just work intuitively (I'm told you can practically guess how something should be done, and it often works), and it really keeps things simple.

Symfony on the other hand is (can be) quite complex, and the learning curve is incredibly steep. I gravitated towards it because of the architectural choices made in the framework, the configurability and service oriented nature of Symfony.

While not necessarily simple or intuitive, once you get over the initial learning curve, Symfony allows you to create very complex and high quality apps in a very short time (relatively speaking).

Back to the question of Laravel and Symfony going together; I think the underlying question is: Is Laravel a valid alternative to Symfony for large scale or complex (enterprise) apps? How about medium scale apps?

(because Symfony can get seriously confusing, the learning curve is terrible)

[modess]

I agree with pretty much everything you say, I wouldn't really say that Symfony's learning curve is incredibly steep though. But it is a bit steeper than Laravels.

Laravel and Symfony go very well together! And if you don't believe me, read this reply by Taylor Otwell, creator or Laravel, on a reddit discussion on the topic of Laravel vs Symfony: http://www.reddit.com/r/PHP...

When it comes to choosing between the two in applications on a larger scale I wouldn't say there's that big of a difference. Laravel will perform slightly worse in benchmarks but the underlying concepts are pretty much the same. Configurability is pretty much the same, and Laravel provides an awesome service oriented nature (service providers).

All in all: you should go with what you feel more comfortable with.

[modess]

Originally posted by Petar Zivkovic on 2014-09-27T21:03Z

---

That's a good discussion on Reddit, thanks for the link.

It's true that Symfony is not too difficult to get started with, but exposing yourself to all of it's features, DIC, building bundles, setting up interfaces to decouple inter-bundle dependancies, and the fact that things can be configured in so many different ways, it certainly makes things more difficult. :D
(but I digress)

I may just try to tackle my next small project in Laravel, it really does look nice!

[modess]

Originally posted by Alex on 2014-11-20T22:36Z

---

A moot post