broken_broken_

7 ms·

1. 61.▲
   by broken_broken_ 3y ago

   Author here, thanks! A second article will cover this, but the bottom line is that it entirely depends on the team and the constraints e.g. is a GC an option (then Go is a good option), is security the highest priority, etc. I’d say that mo
2. 62.▲
   by broken_broken_ 3y ago

   Fair point!
3. 63.▲
   You've just inherited a legacy C++ codebase, now what?(gaultier.github.io)

   380 points by broken_broken_ 3y ago|347 comments
4. 64.▲
   by broken_broken_ 3y ago

   The column type was bytea (basically blob) so it should be stored as is by the database. The profiling showed the hotspots in the gob package directly. The docs explicitly mention that invalid input will make it panic and that can be confir
5. 65.▲
   by broken_broken_ 3y ago

   Just finished removing this encoding in our production services. It panics on malformed input which is a no go for us since high availability is really important for us, and it showed quite a lot in the performance and memory profiles (roug
6. 66.▲
   Roll your own memory profiling: it's not hard(gaultier.github.io)

   2 points by broken_broken_ 3y ago|0 comments