The recent 0.9.2 release prompted me to wonder again about what might be planned
for 1.0. The milestone on GitHub seems quite outdated, aside from the generic
buffering for output plugins (which sounds great). Rob, Mike, do you guys have
any big goals for 1.0? Any timeline?
(I don't personally hav
Thanks for asking, I'm definitely overdue to provide an update. While some of
you might want to know the details of what's going on, I'm sure most of you
don't, so I'll provide two versions of the update:
TL;DR VERSION:
1.0 will be released after generic buffering for all output plugins has la
Thanks a lot for the excruciating detail, I for one appreciated it. I have
written quite a few Go- and Lua-based plugins and from that experience I would
definitely welcome a more unified, event-based API. While the Go API is very
"Go-ish" and open with its direct use of channels, it's not a detail
On Fri, 24 Apr 2015 10:50:11 -0700
Rob Miller wrote:
> My current thinking is that we'll let both of the APIs exist side by side for
> a while. This would mean existing plugins could support buffering, albeit
> with a performance hit, with only trivial code changes. Much improved
> performance
4 matches
Mail list logo
