Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <h1>Ruby on Rails:</h1> <p><strong>Easy to learn?</strong> - Yes - excellent documentation at <a href="http://guides.rubyonrails.org/" rel="noreferrer">guides.rubyonrails.org</a> and a great tutorial at <a href="http://railstutorial.org" rel="noreferrer">railstutorial.org</a>. </p> <p><strong>Easy to build and iterate?</strong> - for sure - rails lends itself to agile and iterative development very well.</p> <p><strong>Easy to deploy?</strong> - To deploy (at least for small apps and while learning), you can't really get easier than using <a href="http://www.heroku.com" rel="noreferrer">heroku.com</a> - git based push and it's free.</p> <p><strong>Popularity</strong> - very popular!</p> <h1>Django</h1> <p><strong>Easy to learn?</strong> - like Rails, Django has excellent documentation at <a href="https://docs.djangoproject.com/en/1.3/" rel="noreferrer">docs.djangoproject.com/en/1.3/</a>. Maybe a slightly steeper learning curve (purely opinion here, but I find rails tends to be "ready to go" whereas django needs a little bit of config before you get into development). </p> <p><strong>Easy to build and iterate?</strong> - again, like Rails, once you are up and running with it, it is pretty easy to iterate.</p> <p><strong>Easy to deploy?</strong> - not as easy as Rails. There are heroku equivalents <a href="https://gondor.io/" rel="noreferrer">gondor.io</a>, <a href="http://djangozoom.com" rel="noreferrer">djangozoom.com</a>, <a href="http://stable.io" rel="noreferrer">stable.io</a> but they tend to be in private beta. That said, I had no trouble getting an invite to <a href="https://gondor.io/" rel="noreferrer">gondor.io</a>. </p> <p><strong>Popularity</strong> - it's popular, but the user community is a little less....lively than the Rails crowd.</p> <h1>Node</h1> <p><strong>Easy to learn?</strong> - um yes and no, easy to put a quick hello world server together, but more tricky if you want a full scale app. I would stay away from this in the first instance - it is new and rapidly evolving. Also, Node itself isn't comparable with Rails or Django because the latter two are frameworks whereas Node is more of a barebones set of apis that you could use to develop something. You could opt for a framework like <a href="http://expressjs.com/" rel="noreferrer">expressjs.com</a> which is more in line with Rails and Django. I've not used it so I can't really give you an opinion.</p> <p><strong>Easy to build and iterate?</strong> - easy to build - yes, easy to iterate - yes.</p> <p><strong>Easy to deploy?</strong> - you can head over to no.de and apply to get a smartmachine - it is free at the moment and easy to deploy - git based.</p> <p><strong>Popularity</strong> - it's gaining.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload