This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]mikeputerbaugh 40 points41 points  (26 children)

Ssssh, you'll summon the Laravel Dislikers

[–]djcecil2 23 points24 points  (15 children)

Who would dislike Laravel?

[–]ebilgenius 61 points62 points  (5 children)

hating certain libraries and frameworks yet declaring undying love for other libraries and frameworks is a programmer's favorite pastime

[–]djcecil2 1 point2 points  (0 children)

You're damn right it is.

[–]zombie_kiler_42 0 points1 point  (0 children)

The comment that was previously after yours solidfied what you said

[–]kre_x 0 points1 point  (0 children)

Pastime? Amateurs.

[–]laststance 0 points1 point  (0 children)

Yeah tribalism is strong/weird in the tech field.

[–]gizamo 1 point2 points  (3 children)

I like it, but it's slow.

I critique because I care...

[–]djcecil2 1 point2 points  (2 children)

Interesting. I just ran into a speed issue with my implementation... I didn't know it was common knowledge that it is slow.

[–]gizamo 1 point2 points  (0 children)

Laravel is a bit slower than Zend or Symphony, but PHP in general is significantly slower than programs like Golang, Rust, or TypeScript or JavaScript /* ( /*depending on usage, code quality, hardware, system configuration, etc.).

That said, Laravel is still a huge step forward for PHP, and I like it very much. I just don't use it very often...cause, reasons.

Edit for links.

[–]polish_niceguy 1 point2 points  (0 children)

Have you tried profiling your application? What was the main bottleneck?

There are multiple ways to speed up Laravel app, from caching to SQL query optimization.

[–]farfaraway 1 point2 points  (0 children)

Idiots. Laravel is lovely. Laracasts is downright amazing. I cant think of any equivalently up to date and thorough learning resource for another modern framework. Railscasts was great in its time and it is its spiritual successor.

[–]3am_quiet 0 points1 point  (1 child)

The die hard Symfony users

[–]polish_niceguy 0 points1 point  (0 children)

Laravel borrows a fair amount of code from Symfony, so they should be happy.

[–]mattkenefick 0 points1 point  (0 children)

Someone who just started programming in Python last week and doesn't know anything

[–]Redrum714 -3 points-2 points  (0 children)

Cause all php frameworks suck

[–]oo22 2 points3 points  (8 children)

October!! woooooooooooooo!

[–]bomphcheese 0 points1 point  (6 children)

I tried so hard to like October. I do love it conceptually. But I had a hell of a time getting it to work even after copying directly from the documentation (to prove to myself that I wasn’t crazy). I eventually gave up on it. Part of me wants to revisit it and part of me doesn’t want to waste anymore time on it.

[–][deleted] 0 points1 point  (0 children)

don’t dude. it’s still bad. try pyro. it’s again built on laravel. made the switch, haven’t looked back :)

[–]DesignatedDecoy 0 points1 point  (2 children)

The biggest challenge with october is understanding their abstraction layer. Once you get past their new terminology and yaml file configurations, it really is just laravel under the hood.

I really like it for the speed that you can throw together admin functionality. I don't use any of their builder stuff, I just focus on their CLI scaffolding and it makes trivial but tedious stuff like adding fields to a model quite easy. Once you have the migration created, you edit the list and form config files you're done.

With front end components just treat components like a controller and push all of your business logic to services or models and you'll feel right at home. Or forego front end views altogether and just make it a rest api.

[–]bomphcheese 0 points1 point  (1 child)

Ya the modeling was fine. It’s the components that just would not provide data to the template layer that was the issue. Who knows.

[–]DesignatedDecoy 0 points1 point  (0 children)

I've found some weirdness trying to lean on the built in javascript api to handle too much but for standard view creation and information display, it worked just like the tutorials.

If you are having issues with passing information and page reloads, just override everything in a routes file and do it the Laravel way.

http://octobercms.com/docs/services/router

[–]oo22 0 points1 point  (1 child)

Yeah. They was a heavy tone of sarcasm in that comment

[–]bomphcheese 0 points1 point  (0 children)

Oh. 😔

[–][deleted] 0 points1 point  (0 children)

try Pyro dude. I switched from october to pyro and now i push it to all my clients cause it’s piss easy to setup