Oh hey, that's my post! Glad someone found it interesting enough to submit.
Don't expect this to hit critical mass by now, but happy to answer questions on the rewriting thing if anyone has any.
Don't expect this to hit critical mass by now, but happy to answer questions on the rewriting thing if anyone has any.
I'll try to find time to go through and attribute things. Thanks for the heads-up!
- I'm a lot more comfortable with Python than I am with shell scripting
- The Python+libgit2 approach _absolutely_ saved time. Being able to iterate through commits in 4-ish hours vs 24 hours for a complete run was huge, and yes, I did a lot of partial runs to test how the process was going.
- Yes, the code rewriting portion ended up as the bulk of the time. I could do a no-op iteration of the commit history in about 30 minutes, and the final processing was about 4.5 hours.
If I ever needed to do this again, yes, I'd use basically the same approach, just with the advantage of applying the knowledge I learned right away.
I'm wondering why you went through the pain of making an HTTP server to process JS files, instead of say putting the temporary file over a ramdisk and running the formatters in parallel over multiple files. Plus, even if it's slow, you only have to run it a few times right?
And no, I was re-running this _dozens_ of times to get it right, especially when I was in the "run -> transform fails on broken JS code -> debug -> write regex -> rerun" portion.