Sinatra

[TR NS]

Ever considered building on Sinatra instead of Rails? How crazy is that?

[Jim Gay]

If there were a compelling reason, I'm sure it would be considered.
But I haven't heard one

On Sun, Jan 20, 2013 at 4:58 AM, TR NS <tran...@gmail.com> wrote:
> Ever considered building on Sinatra instead of Rails? How crazy is that?
>

> --
> Radiant CMS Dev Mailing List
> Post: radiant...@googlegroups.com
> Unsubscribe: radiantcms-de...@googlegroups.com
> Group Site: http://groups.google.com/group/radiantcms-dev/



--
Write intention revealing code #=> http://www.clean-ruby.com

Jim Gay
Saturn Flyer LLC
571-403-0338

[TR NS]

On Sunday, January 20, 2013 8:29:01 AM UTC-5, Jim Gay wrote:

If there were a compelling reason, I'm sure it would be considered.
But I haven't heard one

Should have prefaced my question. I've been reading/considering Radiant's upgrade to Rails 3, and then there's Rails 4 around the corner. The path looks to be something of a nightmare. In all that time Sinatra has barely changed --but not for the lack of use but just b/c it is KISS, and avoids hoisting ever changing conventions on it's users.

[Jim Gay]

This has more to do with tight coupling in general, and I agree.

I went down the path of trying to rewrite radiant my moving the page spec and page model only to find that things were so tightly coupled that I had to bring almost every other model along.

First things first, we need to rearrange a lot to get the app working with Rails 4. It is definitely due for an overhaul, but getting it working on the main platform is the goal. Making it more modular is a major task in itself.