The current stack
Ember.js most likely for the client-side application
Padrino & Ruby for the server-side application
slim for html templates; less for css generation
Ohm/Redis for objects & data structures I want around all the time
my forked Risky/Riak for larger objects & anything with lower access rates, possibly with some redis-objects thrown in
I have a couple thousand lines of working code already with this stack. It’s good enough. Once I decided to pull the trigger and implement I stopped fussing about the choices and just started cranking. It’s all replaceable anyway.
Node.js: I keep wanting to use it for various back-end data services (pushing data to web clients, f’rinstance), but every time I go to write Javascript seriously I want to hunt down its designers and beat them. It’s demented. People are only using it because of V8, I think. I will probably become reconciled to this as I will be forced to write a lot of client-side javascript. I have a vague idea that I might write first cuts of services in Ruby then rewrite in Node for speed. Maybe.
