2,816 karma · joined December 10, 2010
Angel investor in 120+ companies and 10+ funds.
Now working with the French government: https://sylvainzimmer.com/blog/2025/01/public-sector/
All my projects: http://sylvinus.org/
[ my public key: https://keybase.io/sylvinus; my proof: https://keybase.io/sylvinus/sigs/jQNfmDNeTbuL2y1OAPyyoDrd7JYaHnFzi650ZkAWWuw ]
This creates a pseudo ":after" element with content set to the value of the data-hint attribute. Smart!
- Redis has no dependencies either
- "weird responses" from Redis? Do you change your tools the minute they don't behave the way you expect, without investigation?
- The title "Picking the right tool for the job" is the almost opposite of what's done here. It reads more like "Stumbling on cool Go software and picking what job it can do for me"
- 400 (or 850) requests/second are ridiculously low numbers for an in-memory key/value store. Redis is capable of doing 100x that on small/medium machines.
Definitely makes me feel less safe considering the amount of C code there is in tools we depend on.
It will be recorded and posted here as soon as possible ;-)