poadeleted21
Touchdown! Greaser!
- Joined
- Aug 18, 2011
- Messages
- 12,332
Anybody use it? Opinions?
Cake, Zend, Symfony, yii, Codeigniter...all basically do the same, just the syntax and notations differ. There's a number of "reviews" and comparisons found with just a simple search.Anybody use it? Opinions?
Check out Laravel. I have looked extensively at every PHP framework out there. We have a couple large PHP projects and there is nothing that comes remotely close to the Laravel in terms of functionality and beauty.. It is very clean. The guy that created came from a .net background and you can definitely tell it. The ORM is amazing as well the community. If you try it I can assure you, you wont go back. http://laravel.com/
CodeIgniter is freaking awesome. I tried Laravel, but found it more cumbersome to initialize projects with than I had time for, so I went back to CodeIgniter.
I used to be into the whole framework thing but not really anymore. I'd much rather just use Ruby and pick and choose the gems that help me accomplish what I'm trying to do. It's really the best of both worlds.
(I'm a former PHP developer, now ruby developer that does not use rails).
These days basically nobody runs ruby apps on top of Apache. You generally run the app using a web server written in Ruby like Unicorn then put something like nginx in front of that.I thought the same thing until I had the 'A ha!' moment with Laravel. The whole 'migrations' piece of Laravel is nice. I can develop on localhost and tweak my database schema as necessary with the built-in migrations framework. Then when I push the codebase to a DEV or PROD box, all I have to do is run the migrations and my schema is automagically updated. Yeah, I can definitely do that work without the migrations, but it's one less thing to have to worry about when migrating code over to a new box.
As for CI - you might want to check the sustainability of CI going forward. That was one thing that worried me about it - there doesn't seem to be a very defined path with it going forward since the company that picked the project up is looking at dumping it now.
Rails is a HUGGEEE giant beast. It certainly had it's strengths but with the kind of stuff I build it doesn't make sense.
My senior project several years ago was in RoR. The biggest thing that I didn't like about it was trying to get a server that would run it. Maybe if you're ONLY doing Ruby it's easier to go live with, but trying to run RoR over the top of Apache was not the simplest thing to set up (for me, at least, who only dives into Linux command line once every couple of months).
Also, maybe Ruby w/o Rails is easier to set up?