3 ms·
(1) I'm torn on Rails. It's so so so SO much ecosystem to learn just to make a basic web app. I find that I'm much more attracted to Sinatra. Also I prefer Sequ
by sivers 15y ago
(1) I'm torn on Rails. It's so so so SO much ecosystem to learn just to make a basic web app. I find that I'm much more attracted to Sinatra. Also I prefer Sequel to ActiveRecord. Also, I really want to try playing with the architecture of a JSON REST API back-end and a JavaScript front-end (like Backbone.js). So for that, it seems Sinatra + Sequel suits me better. I'm trying this way for now, and if it doesn't work out, I'll commit a few hundred hours to learning Rails whole ecosystem. (Then I guess keeping up with it constantly.)
(2) Oooh. Good question. It wasn't advice that made the difference. It was a style of teaching. Standing above me, pushing me further than I knew, but somehow still on the edge of my abilities. Making me figure things out for myself instead of giving me the answer.
The closest I've seen someone come to systemizing it is Code School : http://www.codeschool.com/ http://www.codeschool.com/
I love that style of "here's a little info, now figure out this problem."
- daspanters 15y agoYou have no idea how valuable your responses are to me, I consider it a priviledge that you took the time to answer my questions, thank you very much! I like the idea also of going Sinatra, use Rails functionality if needed but otherwise keeping it simpler, there is always the chance to go with the full-blown version (Rails). Thanks again for sharing and taking the time!