4 ms·
> In summary: by moving from maps to arrays. That may seem like an awfully pedestrian observation, but it certainly wasn’t obvious to us at the outset that thi
by jnordwick 4y ago
> In summary: by moving from maps to arrays. That may seem like an awfully pedestrian observation, but it certainly wasn’t obvious to us at the outset that this was the crux of the problem!
How is this not your first thought !?!? Why would you even build it on maps? (at least trees I hope, please dont say hashes, I'll die a little inside if you do.)
- iampims 4y agoParaphrasing the article: “Rewriting from JavaScript to Go is already a big ordeal, so a lift and shift approach is what we went for” An interesting follow-up question would be: would they have seen the same improvements had they stuck with JS and replaced maps with arrays.