Dispelling some confusion about SproutCore
Posted on June 17th, 2008
by charles
whump says:
While SproutCore uses Ruby to generate static HTML and JavaScript files, you are not tied to Ruby or Rails in production.
SproutCore runs in the browser, your production system can use whatever backend you want, as long as it sends JSON to the browser.
This is true, though you could use any format; not just JSON. JSON is faster though because it is simpler in structure. Most browsers I tested could parse incoming JSON 10x faster than they could setup DOM for XML.
Anyway, whump’s post is a good clarification about using SproutCore with non-ruby backends from someone who has been there.
Read Dispelling Some Confusion About SproutCore
So i want to know, can I use rails with sproutcore together?
If y’all could provide a full RSS feed instead of the abbreviated on, I (for one) would very much appreciate it!
Bill: Done.
The SproutCore docs say that it uses Rubinius, a language based on Ruby, for templating (http://www.sproutcore.com/documentation/hello-world-tutorial-2-your-first-viewsadsteste/). This is incorrect. You’re using ERB, a templating language written in Ruby. Rubinius is a new Ruby VM, Rubinius is not a templating language.
Allen,
I’m sure you could use Rails as your backend and just send JSON as responses. I think that Rails 2.1 automatically parses JSON params as well.
[...] no secret Apple have been using the SproutCore framework in producing Me.com and that while SproutCore isn’t tied to Ruby on Rails it seems likely Apple went with Rails given the lack of interest in WebObjects and more and more [...]