6 ms·
I'm always bit sceptical of "our rewrite in new language is quicker" stories. If I were to rewrite something in the same language as v1 t would probably be quic
by macca321 7y ago
I'm always bit sceptical of "our rewrite in new language is quicker" stories. If I were to rewrite something in the same language as v1 t would probably be quicker.
Actually that's not true, I'd probably get bored and then just ry to get the damn thing working as well as v1 used to and then go on holiday without optimising.
- esr 7y agoThing is, it wasn't a rewrite. I deliberately did as dumb and literal a translation as I could because I feared that if I tried to change the code wile translating it the complexity of the job would spiral out of control. One reason this is clear in my mind is that we did do a lot of serious optimization after the dumb straight-line translation first passed my test suite. Because we could; Go's profiling tools are much, much better than Python's - in fact they're better than for any other language I've used. Interestingly, one of the early results from profiling was t - once we got rid of one O(n2) that only blew up on stupidly large repositories like GCC's - the profile didn't show any of the usual kind of 80/20 hotspots. The biggest box was GC - the Python code had already been really well optimized. Er, who knew? That makes this a particularly good language vs. language comparison.