That's right. But it does reduce the cost of a compromised server. Since no passwords are stored in the server itself, if it's compromised, the user's passwords won't be exposed (even if they're encrypted, they're often weakly encrypted, especially as time goes by).
And/or they simply want to avoid a direct confrontation, which might happen when a man is present, but not when the woman is alone. This just happened to me today, biking and of course i heard some rude comments. Really wanted to tell them to fuck off but then I would engage, they might respond, etc, and my biking zen would be even more disturbed.
Last i saw, django uses 1000 as the iteration count for PBKDF2. So maybe that's common nowadays and needs to be reviewed. On another point, can anyone point me to an article explaining the state of the art for user passwords storage?
Taking into account the normal backlash that ensues against any woman who raises issues of sexism in the workplace, i think she was very brave. typical reaction is let's not judge company A but let's really judge the woman, instead of the more sane reaction of let's not judge either the woman or the company. as for going to court, i know plenty of people who bitch about the workplace publicly and never go to court. the only difference is harassment is actually a crime but proving it is typically hell so most woman don't bother (and it could hurt them real bad professionally) - they just deal with it the best they can. Anyway, let's not judge either github or julie - they both deserve fair treatment.
They were being idiots and violating the code of conduct of pycon, and YES, it does apply to private conversations that others can't avoid hearing since they're in a public place. She shamed them rightly. As for them being fired, that was the company's call - who employed them. Now an anonymous guy posts this, she explains the whole sequence and in the end it's her fault. No, the responsability lies with who made the inappropriate comments in the first place and with who employs/employed them.
Thanks for your feedback. I've been playing around with both languages, and was leaning towards scala since it seemed more likely i could use it professionally, even though i liked clojure a bit more, sortta like the lisp like syntax.
out of curiosity, why did you go the clojure route instead of the scala route? From what i understand, scala has more libraries available, including ai and nlp libraries but maybe my impression is not correct?
is there any known algorithm that looks at the relationship between cached items? Ie. File A is accessed, then B, then C, then D, then E, and so on. A would a have stronger relationship to B, one step away, than to D, two steps away. So if we later access file A, the algorithm would know there's a higher probability that we need File B next, so it could check if file B is in the cache and if not, prefetch it and save it in the cache.
thank you! i'm going through practical common lisp and i've been missing exactly this. as i've been reading through i wish practical common lisp had a reference on each function so we don't have to go back to the chapter where it's defined to remember the function's signature. now i'll print this.
signed up, and been loving it! for now no slow downs of gmail. Is there any way to group boxes together? I created one box per client for some of my clients thinking i would put each issue in there and then figured out that i would have to create a box for each issue. so how do i group boxes, eg those belonging to the same project?