Re: [go-nuts] [ANN] Gleam now supports distributed pure Go Map Reduce

Thanks Chris! I'll go through the documentation to understand this new approach. Pablo On Mon, Jan 23, 2017 at 12:19 PM, Chris Lu wrote: > Thanks! This page has a little more details. > > https://github.com/chrislusf/gleam/wiki/Write-Mapper-Reducer-in-Go > > LuaJIT is fast. But Go code is more

Re: [go-nuts] [ANN] Gleam now supports distributed pure Go Map Reduce

Thanks! This page has a little more details. https://github.com/chrislusf/gleam/wiki/Write-Mapper-Reducer-in-Go LuaJIT is fast. But Go code is more manageable and can have more complicated logic with libraries. Sacrificing the readability with extra type casting from interface{} seems a small cos

[go-nuts] [ANN] Gleam now supports distributed pure Go Map Reduce

That's great news Chris! Is it documented anywhere with some more detail this pure Go implementation? I'd love to know more about how you overcame the initial problems such as external code execution that lead you to choose LuaJit in the first place. Thanks, Pablo -- You received this message

[go-nuts] [ANN] Gleam now supports distributed pure Go Map Reduce

See https://github.com/chrislusf/gleam/blob/master/README.md Many people may know Gleam used to support only LuaJIT for distributed map reduce. After several rounds of re-thinking, I came down to this syntax to do it via pure Go. Please let me know whether it seems ok or can be better. Chris