On Thursday, August 30, 2018 at 1:32:18 PM UTC-4, Akram Ahmad wrote: > > Your work on porting *reposurgeon* (from Python into Go) for improved > performance sounds very cool, Eric (BTW, your work in, and musings on, Lisp > and UNIX have been a huge influence on my evolution as a programmer. Kudos > for that! >
Thanks for the kind words. I have rather been forced into this. In cooperation with the GCC devteam, I'm trying to move their repository from Subversion to git. It's so freaking big and Python is so slow that test conversions are taking more than 9 hours, with occasional OOMs because the working set is so huge. I have got to reduce that cycle time, it is making forensics on the malformations in the history effectively impossible. Go seems to be a tool that fits the job - translation of a smaller auxiliary program suggests I ca n reasonably expect a 40x speed increase - but this is my first major project in it and I have not yet mastered the language. Once I do, I expect it to replace C for all my new projects that would otherwise have been C. Also anything I would havew written in Python that needs to perform at machine speeds rather than human speed. -- 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.
