2 ms·
". I love that I can whip out a 2-file application in Sinatra --- one file for the Ruby and templates, and another for the jQ js that'll run on the client." Ye
by jamesbritt 17y ago
". I love that I can whip out a 2-file application in Sinatra --- one file for the Ruby and templates, and another for the jQ js that'll run on the client."
Yeah, I love that about Ramaze as well. :)
"What does Ramaze do better than Sinatra for me?"
Appears to be faster (at least in some simple benchmarks I ran). Choice of templating language may be key.
Has a better-sized set of robust standard helpers, should you want to load them.
More built-in adapters for a wide variety of template engines (Haml, Ezamar, Liquid, Markaby, others)
Unbeatable community on irc (#ramaze on freenode)
Way cooler shirts and coffee cups: http://www.cafepress.com/rubystuff/4904578 http://www.cafepress.com/rubystuff/4904578 ;)
Whether or not any of this works out as "better" for anyone is hard to say. I like that Sinatra doesn't dump a ton of must-load crap on you just to get started, but neither does rolling a plain Rack app. Or Ramaze, for that matter.
It's also nice to have a reliable set of built-in libs to pull from, and as best I can see there's a stronger choice in Ramaze.
But, to be honest, Sinatra just never showed enough value to me to dig into all it's possibilities, so I may be wrong in my observations.
- tptacek 17y agoThanks. Helpful! Appreciated.