Why I wouldn’t use Rails for a new company

Re:Why I wouldn’t use Rails for a new company by 0x0 on Thursday September 17, 2015 @06:08PM (#10236374)

There was a pretty elegant post on how Python's coroutines can replace callback hell with almost-synchronous-looking async code on HN the other day: https://news.ycombinator.com/item?id=10220712

Wonder if something similar will catch on in the node ecosystem?

[ Parent | on HN ]

Re:Why I wouldn’t use Rails for a new company by supster on Thursday September 17, 2015 @07:04PM (#10236617)

Yeah ES7 has async and await which are pretty similar to that

source: http://www.sitepoint.com/simplifying-asynchronous-coding-es7...

[ Parent | on HN ]

Re:Why I wouldn’t use Rails for a new company by lastofus on Thursday September 17, 2015 @06:23PM (#10236455)

Everyone forgets that Gevent has been around for years, and lets you write completely synchronous looking async code.

[ Parent | on HN ]

Re:Why I wouldn’t use Rails for a new company by vangale on Thursday September 17, 2015 @06:51PM (#10236575)

I think a better way of looking at it is there isn't enough "cross pollination" in big open-source frameworks and languages.

[ Parent | on HN ]

Re:Why I wouldn’t use Rails for a new company by M2Ys4U on Thursday September 17, 2015 @06:41PM (#10236530)

promises, async functions and generators will make writing async code look more sync in javascript/node.

Whether or not this is a good thing or not, I'm undecided.

[ Parent | on HN ]