2,911 karma · joined August 10, 2018
(I use Firefox now)
Not to mention the inconsistent tests that fail so randomly from timing issues that the team ignores them
Edit: never mind, your article named it as a good choice
Every time I ask somebody about this, they recommend slightly different practices or else insist that you can’t use a checklist approach. I partially rolled my own auth as an experiment to see what they meant and it seemed not too difficult, but I worry I missed things and hesitate to use it for production.
(Still used libraries though like bcrypt and a session encryption library)
Having it sleep for 100ms per request is a little strange for nodejs though because it is basically simulating cpu load, even though a node server typically hands off work to an optimized library that might be disk or network io bound instead of cpu bound. 100ms is a lot of cpu work per request, no? That is specifically the sort of task node is not recommended for, since it focuses on async.
Maybe I’m wrong, I need to work on larger projects to see what loads are more typical. At my last job, the entire focus was to use node to redirect work to c++ code, databases, etc, basically just request routing.
Still, this looks rough for node. 2x to 4x difference between it and the fastest is still a significant cost for such a nice backend to work with
Best thing overall is to just wear synthetics that dry very quickly (pair with waterproof bag for your backpack contents - trash compactor bags are amazing for weight efficiency)
There was another front page story today about a judge claiming that the wiki claims could not be tried because they could not confirm whether the government was indeed spying. Which is it: are the leaked documents real or fake? Awfully convenient interpretations