sawzall

[Kees Varekamp]

I just watched http://channel9.msdn.com/Events/Lang-NEXT/Lang-NEXT-2014/From-Parallel-to-Concurrent and I am now kind of interested in Sawzall.

Rob Pike says somewhere at the end that Go is partly the replacement of Sawzall.

Does anyone know if there are plans to open source (parts of) that (like the szl compiler/runtime)?
Has anyone ever attempted to port szl itself to Go?

[David Symonds]

https://code.google.com/p/szl/

[andrewc...@gmail.com]

Rob mentioned that Go was part of the replacement for Sawzall. Perhaps a new interpreter/runtime for a new propriety system is written in Go (or compiles to Go) . Something like that might be a sensitive Google secret as he didn't seem to want to go into detail in that talk.

[Kevin Gillette]

If I recall correctly, although Sawzall itself is now open source, SawMill is not. Essentially what you're left with is a solid parallel language without the massively-parallel execution engine (which, with all likelyhood, is strongly coupled to many proprietary Google components).

[Rob Pike]

The interpereter and compiler, with a simple non-parallel table
implementation, are available at code.google.com/p/szl. It's not my
doing to open source it, and the code there is the work of many
besides myself, but it works. Several outside groups have taken that,
extended it, hooked it to hadoop, and so on.

I haven't looked at this stuff in many years, so you're on your own.
Plus it's C++, because <see talk>.

-rob

> --
> 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...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Kees Varekamp]

OK thanks all

I'm guessing no one has ported szl to Go then. It would be cool to have but a big job.

[andrewc...@gmail.com]

Does the implementation language matter to the user? (Only really for the purpose of extension.)

[Kees Varekamp]

yes, easier to extend (especially new data providers and new table types), and also to embed into various go servers. I don't really speak c++