3 ms·
That's why you have to tag the value with an identifier of the algorithm, so you can change your mind later. The problems they currently face are a direct conse
by toolslive 11y ago
That's why you have to tag the value with an identifier of the algorithm, so you can change your mind later. The problems they currently face are a direct consequence of an architectural mistake a few years ago.
- jfb 11y agoMaybe; maybe not. Regardless, they aren't in a position to alter their software to the degree required at this time.
- robn_fastmail 11y agoIndeed. As I note in the post, this wasn't something we _needed_ to do at that time, we were just curious. Replacing a function with a faster implementation is trivial; its just another deployment and we do several of those each week. Changing data format adds operational complexity - two codepaths need to be run and maintained and we increase system load and lower response times for the duration. (The data format is versioned, so that's easy - no architectural problem there). Its totally worth doing if you need to, and we're not afraid of that, but you don't do it on a whim - it takes proper planning and testing and needs multiple people involved.