Ruby Frameworks? Which one? Bye bye Rails.
slideshare.net
Ruby Frameworks? Which one? Bye bye Rails.
1–10 of 93 posts
Re: Ruby Frameworks? Which one? Bye bye Rails.
#2100x this. I hope Padrino picks up more steam and people it give it more love. It absolutely kicks ass and I would choose it over Rails everytime now.
Now, if someone would write Padrino with Python, I'd be one really happy camper!
Re: Ruby Frameworks? Which one? Bye bye Rails.
#3I definitely love Sinatra, and I'm impressed by the admin interface, but it looks like there's no support for DataMapper as an ORM.
I also wonder if this is just turning Sinatra into Rails. I think for the now I prefer to just build a Sinatra app and add gems and plugins as I need them.
Re: Ruby Frameworks? Which one? Bye bye Rails.
#4Looks like a Xitrum (Scala web framework) to me.
Re: Ruby Frameworks? Which one? Bye bye Rails.
#5I definitely love Sinatra, and I'm impressed by the admin interface, but it looks like there's no support for DataMapper as an ORM. I also wonder if this is just turning Sinatra into Rails. I think for the now I prefer to just build a Sinatra app and add gems and plugins as I need them.
The thing I like the most about it is the part where they demonstrate selectively including certain elements into Sinatra. I like Sinatra exactly because it doesn't come with the kitchen-sink - like you I prefer to just add gems and plugins as I need them (and I rarely find I do), but if I do I might look at Padrino.
(As for the admin interface, their site claims it has DataMapper support)
Re: Ruby Frameworks? Which one? Bye bye Rails.
#6This reminds me of Flask for Python (nb. although more is built in to Padrino, most of the functionality for Flask is provided by plugins). I've recently started using Flask for new projects in favor of Django. I feel that most of the libraries I use are framework agnostic, stuff like ORM (SqlAlchemy), PDF generation, redis/mongodb adapters etc, so being able to pick what fits and leave the cruft out is great.
But besides that, I feel that in recent times development is moving much more to the client - and client code like Javascript/CoffeeScript, Java for Android and Objective C, is getting much bigger at the expense of server side code. This is recently evidenced by the new 37signals Basecamp Next app which is 50/50 CoffeeScript/Ruby.
So the server side programming is on track to becoming "just" a API endpoint for all these different technologies and I think micro frameworks like Flask and Padrino are very well suited for that.
Re: Ruby Frameworks? Which one? Bye bye Rails.
#7I definitely love Sinatra, and I'm impressed by the admin interface, but it looks like there's no support for DataMapper as an ORM. I also wonder if this is just turning Sinatra into Rails. I think for the now I prefer to just build a Sinatra app and add gems and plugins as I need them.
Same here. I really like Sinatra's gem ecosystem, and with unobtrusive Javascript I don't have much framework-dependent code on the views, nor helpers like his link_to confirm example, in the presentation...
I admit that sometimes I miss generators, but Sinatra's boilerplate code is so minimal that I just don't care much anymore.
Re: Ruby Frameworks? Which one? Bye bye Rails.
#8Padrino is really nice web framework for Ruby. I have used it for experimental projects.
My work was using latest Padrino framework at work, but extremely unhappy with the its performance (slow response). We had ported the app to Rails 3.1 for better performance. (We will upgrade it to 3.2 soon)
In fact, I think Padrino is pretty ideal for personal and small apps. Not really ideal for medium to large apps.
Just my opinion and experience.
Re: Ruby Frameworks? Which one? Bye bye Rails.
#9As someone that's just crossed a year or Ruby/Rails learning, having scaled the majority of the now massively steep learning curve, I'll stick with the complexity that is Rails.
Re: Ruby Frameworks? Which one? Bye bye Rails.
#10Padrino is great for small apps but for medium to big projects I much prefer go the rails way and remove the parts I don't need.
You can remove the big rails modules if you don't need them (activesupport, activemailer, activerecord,. ..) but also the rack middlewares.