Daniel Schierbeck
Daniel Schierbeck
As in, how is it used in the UI?
@delner OK, I've thought of another use case for "components" – we have a handful of extremely large monoliths, and those have _split_ ownership, on-call rotations, etc. We use Github...
I would prefer flexibility for "component". It's less important for there to be a standard about what it means than it is for it to support the use cases that...
@ABaldwinHunter I've implemented something similar to this in https://github.com/zendesk/ruby-kafka. The code is still early beta, but I would love it if you would give it a look.
This issue is fixed by https://github.com/zendesk/ruby-kafka.
@trans: regarding Ruby 2, the proposed syntax should be flexible enough to cover those cases. Regarding #17 - it seems to me that @mojombo's argument against that syntax was that...
It's not allowed in the current specification (http://tomdoc.org/), and I'd rather not change that.
@trans: that's really an issue for, well, another issue.
@mojombo BUMP
It's mainly due to line length considerations - I try to keep lines below 80 chars, but it can be difficult when there's a method with both a long argument...