Hacker News new | past | comments | ask | show | jobs | submit login

That makes sense. Sorry for the assumption.

Guilds felt omitted in your post since they (should) address one of the points you make about the usability/ergonomics of existing Ruby APIs for managing non-sequential execution.

But it’s definitely a bit early to tell what Guilds will actually look like as a final product.




Guilds are just a fancy name for threads or processes at this point. What they ultimately end up being is yet to be seen :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: