Thanks for the question! It's nice that you know glow. Gleam is very similar to glow, but has a very different approach after some rethinking.
Glow is based on channels and reflection, which are less performant. There is a performance comparison example: https://github.com/chrislusf/gleam/blob/master/examples/pi_estimation/pi_estimation.go Glow is based on pure go, which is not flexible to dynamically change execution path. It's hard to build more advanced generic use cases. With Gleam, we can build a distributed SQL execution engine, for example. Gleam uses Luajit. Lua is small and simple. Luajit has performance comparable to C, Java, and Go, and it comes automatically with "generics". It is a nice compliment to Go for distributed computing. Chris On Mon, Oct 10, 2016 at 4:53 PM, Mandolyte <cecil....@gmail.com> wrote: > How is this connected with your glow package? Layered on top of? > > -- > You received this message because you are subscribed to a topic in the > Google Groups "golang-nuts" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/golang-nuts/CuxsXzyd4Eg/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
