Promises are going to solve this problem in an elegant way, expect it in next major release.
That said, I've release a client/server game (online sailing regattas) in Elm & Play/Scala with websockets, and current API was enough for me:
https://github.com/etaque/tacks
One friend of mine did the same, here in France: high level degree, but only one year working in front of a desk. He totally switched to a sailing instructor job. As a computer engineer and sailor, that's really appealing me, but my skin wouldn't bear it. I know he's 100% living during the day, I know I'm making mouldy on my chair...
I can relate 100%. I have a good friend who quit his desk job in finance to go to Marine OCS. He runs around in the woods, climbs on mountains, and sleeps on the ground everyday. This might be dumb, but I feel like he's already done more with his life than I ever will.
Anyway, that's why I'm supporting my job : that mental and physical reboot through sailing every week-end became essential to me. Finding your own weekly brainwasher is a fair compromise !
That's what I got from it too. The framework being this flexible should help a DBA fully use the database to his advantage. The project I work on has had to do some non standard things with Rails and it's flexibility has made it much easier. In our view rails and it's default are a starting point providing the basic infrastructure to get the project going, not an end all be all solution. I see the same thing in NoSQL solutions, they try to give the developers and DBA as much flexibility as possible. They don't really seem to offer any default. RDBMS is basically the sensible defaults without the flexibility. Maybe the in between can be found.
I'd love to get into that, but given that my only sailing experience is 420s and FJs on a lake that never had any wind, I think I should probably start with something a little less hard to handle. ;-) Know of any dinghy sailing schools in the South Bay?
