4 ms·
I think what raggi said is that there are no good _open source_ _complex_ async _apps_, mostly because when people are writing open source they tend to write li
by mtoledo 16y ago
I think what raggi said is that there are no good _open source_ _complex_ async _apps_, mostly because when people are writing open source they tend to write libs, not apps, or end up not working anymore at the problem before it gets really complex.
I've worked on a commercial, complex, async codebase with raggi and have to agree that there is a way other than callback-hell, even for complex evented applications.
In my personal opinion, even more so on ruby than javascript, but I don't want to get to that really.
edit: changed asterisks to underscores because I didn't know they'd be italicized
- moe 16y agoStill sounds dubious to me. Then why has this pattern not emerged as best practice long ago? And, frankly, I'd be curious to see a snippet of code in that style.
- mtoledo 16y agoyea I don't doubt it. the reason it hasn't surfaced as a best practice yet is probably because best practices for async programming haven't been a hot topic yet either. and the point is exactly that a snippet doesn't fit the bill. its easy to abstract complexity on a snippet. its only with the full fledged solution that you start to see best practices emerging and making a difference.
- raggi 16y agoSince when was it not a good practice to encapsulate, abstract, and decouple?