Comments on: How to Build Sinatra on Rails 3 http://yehudakatz.com/2009/08/26/how-to-build-sinatra-on-rails-3/ Random Geek-Related Thoughts Wed, 08 Sep 2010 23:53:11 -0700 hourly 1 By: Jônatas Paganini http://yehudakatz.com/2009/08/26/how-to-build-sinatra-on-rails-3/comment-page-1/#comment-18393 Jônatas Paganini Tue, 16 Feb 2010 13:06:00 +0000 http://yehudakatz.com/?p=317#comment-18393 I've been using Sinatra pure, but when I need to get a confortable place to code, I require the actionpack, actionview and a bunch of cool gems. This wasn't my best choice, I think that the best is combine Rails 3 whith a Rack's powerful. I’ve been using Sinatra pure, but when I need to get a confortable place to code, I require the actionpack, actionview and a bunch of cool gems. This wasn’t my best choice, I think that the best is combine Rails 3 whith a Rack’s powerful.

]]> By: jd http://yehudakatz.com/2009/08/26/how-to-build-sinatra-on-rails-3/comment-page-1/#comment-18127 jd Mon, 01 Feb 2010 05:07:51 +0000 http://yehudakatz.com/?p=317#comment-18127 A very nice proof of concept. Actually it's funny to see how Rails3 became kind of the Light Framework by (simply?) having it more object-oriented/modular. Thanks for this series of features and use-cases reviews, Yehuda! A very nice proof of concept. Actually it’s funny to see how Rails3 became kind of the Light Framework by (simply?) having it more object-oriented/modular. Thanks for this series of features and use-cases reviews, Yehuda!

]]> By: Arjun Ghosh http://yehudakatz.com/2009/08/26/how-to-build-sinatra-on-rails-3/comment-page-1/#comment-17348 Arjun Ghosh Mon, 09 Nov 2009 23:01:43 +0000 http://yehudakatz.com/?p=317#comment-17348 Yehuda, very nice and useful post on people getting introduced to Sinatra Yehuda, very nice and useful post on people getting introduced to Sinatra

]]> By: Tomás Pollak http://yehudakatz.com/2009/08/26/how-to-build-sinatra-on-rails-3/comment-page-1/#comment-17139 Tomás Pollak Tue, 15 Sep 2009 11:01:03 +0000 http://yehudakatz.com/?p=317#comment-17139 Nice one Yehuda. I can wait to try out Rails3 and see how "merbizised" it has become (i.e. leaner & meaner :). Nice one Yehuda. I can wait to try out Rails3 and see how “merbizised” it has become (i.e. leaner & meaner :).

]]> By: Tj http://yehudakatz.com/2009/08/26/how-to-build-sinatra-on-rails-3/comment-page-1/#comment-17076 Tj Sun, 30 Aug 2009 21:39:16 +0000 http://yehudakatz.com/?p=317#comment-17076 Sinatra is better than Rails IMO with a few abstracted libraries it is nearly as powerful without most the cruft Sinatra is better than Rails IMO with a few abstracted libraries it is nearly as powerful without most the cruft

]]> By: Ho-Sheng Hsiao http://yehudakatz.com/2009/08/26/how-to-build-sinatra-on-rails-3/comment-page-1/#comment-17073 Ho-Sheng Hsiao Fri, 28 Aug 2009 22:03:23 +0000 http://yehudakatz.com/?p=317#comment-17073 Ever since I saw the slides from Katz's presentation in Japan, my head has been spinning with the possibilities. They are based on the following assumptions: (1) Each of the module can be swapped out because they comply with APIs ... taking Ruby ducktyping to the next level. (2) The concept of ActiveMailer and ActiveController having shared code in AbstractController means the possibility of using non-HTTP dispatches and routing. So talking with @rahsunmcafee (twitter), we came up with some of the implications: * A real Wordpress-like engine instead of faking it with Rails 2. One that lets you set up a blog very quickly, yet when it comes time to add embedded apps, you have the entirety of the Rails 3 stack to work with (the best parts of Wordpress minus its worst parts). * A real Django/Drupal/etc.-like CMS engine instead of faking it with Rails 2. * A CRM that doesn't have to struggle (like XLSuite). * A workflow engine that can talk Rack Endpoint instead of rolling your own ad-hoc bridge. * Pure email applications that can be driven through a SQL (or NoSQL) backend and erb/haml/whatever templating. * HTTP-Bosh dispatcher. Or better yet, an XMPP listener/dispatcher: a framework for building Google Wave apps (while taking advantage of AR/Datamapper/Sequel/et. al) * AMQP dispatcher? Might as well talk about asynchronous, stateful dispatches. How about being able to play well with the weird merchant gateway protocols? From where I'm standing, it seems to me the major thing about Rails 3 is the ability to change the convention itself to fit the app you are writing. It's not so much that you can reconfigure Rails 3 so much as rebuilding Rails 2 using Rails 3 components -- just like creating that Sinatra DSL using Rails 3 components. It means you can create a DSL specific to an app yet have it play nice without fighting against Rails 2 conventions. And if you just want to work with Rails 2 style apps, you still can. Ever since I saw the slides from Katz’s presentation in Japan, my head has been spinning with the possibilities. They are based on the following assumptions:

(1) Each of the module can be swapped out because they comply with APIs … taking Ruby ducktyping to the next level.

(2) The concept of ActiveMailer and ActiveController having shared code in AbstractController means the possibility of using non-HTTP dispatches and routing.

So talking with @rahsunmcafee (twitter), we came up with some of the implications:

* A real WordPress-like engine instead of faking it with Rails 2. One that lets you set up a blog very quickly, yet when it comes time to add embedded apps, you have the entirety of the Rails 3 stack to work with (the best parts of WordPress minus its worst parts).

* A real Django/Drupal/etc.-like CMS engine instead of faking it with Rails 2.

* A CRM that doesn’t have to struggle (like XLSuite).

* A workflow engine that can talk Rack Endpoint instead of rolling your own ad-hoc bridge.

* Pure email applications that can be driven through a SQL (or NoSQL) backend and erb/haml/whatever templating.

* HTTP-Bosh dispatcher. Or better yet, an XMPP listener/dispatcher: a framework for building Google Wave apps (while taking advantage of AR/Datamapper/Sequel/et. al)

* AMQP dispatcher? Might as well talk about asynchronous, stateful dispatches. How about being able to play well with the weird merchant gateway protocols?

From where I’m standing, it seems to me the major thing about Rails 3 is the ability to change the convention itself to fit the app you are writing. It’s not so much that you can reconfigure Rails 3 so much as rebuilding Rails 2 using Rails 3 components — just like creating that Sinatra DSL using Rails 3 components. It means you can create a DSL specific to an app yet have it play nice without fighting against Rails 2 conventions. And if you just want to work with Rails 2 style apps, you still can.

]]> By: wycats http://yehudakatz.com/2009/08/26/how-to-build-sinatra-on-rails-3/comment-page-1/#comment-17072 wycats Fri, 28 Aug 2009 20:00:20 +0000 http://yehudakatz.com/?p=317#comment-17072 @dreamcat4 two things 1) It's just a demo to show the flexibility of the new Rails architecture; you're probably better off using Sinatra for Sinatra. 2) You can pull in any of the advanced functionality of Rails for free into a Railsnatra app. For instance, to use conditional GET, simply pull in the ConditionalGet module and fresh_when at al will simply work. The implementation in this blog post is just a demo, but if someone wanted to take up the banner they could make it work quite well. @dreamcat4 two things

1) It’s just a demo to show the flexibility of the new Rails architecture; you’re probably better off using Sinatra for Sinatra.

2) You can pull in any of the advanced functionality of Rails for free into a Railsnatra app. For instance, to use conditional GET, simply pull in the ConditionalGet module and fresh_when at al will simply work. The implementation in this blog post is just a demo, but if someone wanted to take up the banner they could make it work quite well.

]]> By: dreamcat4 http://yehudakatz.com/2009/08/26/how-to-build-sinatra-on-rails-3/comment-page-1/#comment-17071 dreamcat4 Fri, 28 Aug 2009 19:25:26 +0000 http://yehudakatz.com/?p=317#comment-17071 Now sure why you'd benefit more from this method. It seems like a lot of re-writing of the Sinatra code. You might otherwise specify sinatra as an extra rack middleware layer in your config.ru file. Still have access to some rails environment, for example the activerecord models. An evolution of Pratik's method. See http://bit.ly/19bYmP, http://bit.ly/5T51g Now sure why you’d benefit more from this method. It seems like a lot of re-writing of the Sinatra code. You might otherwise specify sinatra as an extra rack middleware layer in your config.ru file. Still have access to some rails environment, for example the activerecord models. An evolution of Pratik’s method. See http://bit.ly/19bYmP, http://bit.ly/5T51g

]]> By: cbmeeks http://yehudakatz.com/2009/08/26/how-to-build-sinatra-on-rails-3/comment-page-1/#comment-17070 cbmeeks Fri, 28 Aug 2009 17:14:05 +0000 http://yehudakatz.com/?p=317#comment-17070 Yehuda, that is awesome. But a little over my head right now. lol @Geoffrey first, I thought you were kidding but I could actually see a use for this. Drupal on Rails? :-) Yehuda, that is awesome. But a little over my head right now. lol

@Geoffrey first, I thought you were kidding but I could actually see a use for this. Drupal on Rails? :-)

]]> By: Guoliang Cao http://yehudakatz.com/2009/08/26/how-to-build-sinatra-on-rails-3/comment-page-1/#comment-17067 Guoliang Cao Fri, 28 Aug 2009 13:30:58 +0000 http://yehudakatz.com/?p=317#comment-17067 Very cool! Thanks. Very cool! Thanks.

]]>