set -o vi
744 karma · joined May 8, 2008
In fact, due the lack of side effects it's much easier to do than with procedural code.
Mark Pilgrim is alive/annoyed we called the police. Please stand down and give the man privacy and space, and thanks everyone for caring. ... The communication was specifically verified, it was him, and that's that. That was the single hardest decision I've had to make this year.
Price(uptime) = K*(1/1 - uptime)
so I would ask for infinite dollars...
http://openclassroom.stanford.edu/MainFolder/CoursePage.php?...
The reference course on Stanford is CS229A instead of CS229, which is much lighter on Math. I have watched the videos on Linear and Logistic regression and the hardest derivations are elided, while the emphasis is put on intuitions.
Which would be silly because their "OS" is much more limited than Windows 7, even the Starter version, and its only compelling feature would be to run on much cheaper hardware.
I'm among the few unimpressed by list comprehensions. I use them because they're "idiomatic", but I'm equally comfortable with good old map(), which, I admit, it may be equally foreign for imperative-only programmers.
About the xrange() example, IIRC the iterator protocol predates generators, and probably is easier to grasp since the state is handled explicitely.
Decorators, as Lisp macros, are powerful but, if not handled with care, the source of very subtle bugs, because the thing you're looking at(the decorated function) doesn't do what it seems to do.
Anyway I'm not arguing against this artifacts, just pointing that, some of the merits of Python that were true a decade ago, aren't anymore.
I would say that's unarguably marginally better. What provides Python 3 that I miss in Python 2? For me nothing at all. Ok, dealing with Unicode it's easier. So what? Optional type annotations, that's something I would miss.
Still, I think he's been careless. If you really want to give your users a "recover password"(especially after you have reached success), do it in a sensible way. Use hardened authentication servers behind inspection firewalls(preferably encrypted so filesystem access isn't enough!!) but don't store them in the same database as the rest of your data. Or use hashes and store the plaintext(encrypted) in another system which will do the mailing.
There are lots of options, none of them as good as slow-hashes-only solutions, but a better compromise between security and UX.
Where is the conflict?
Besides, most people I know, would pay 100$ for the ability of running a "real" OS.
Then you publish the fact itself and the algorithm in your blog(real name), which, besides, doesn't depend on a passphrase (which could turn your method in a sort of dual factor authenticator).
The paper could be photocopied and returned to your wallet and you'd never know.
Please, don't talk me about how many bits of entropy your passwords have. They aren't secure.
OK, it ain't perfect. Things usually doesn't fail in a uniformaly distributed way and you can't be sure you'll see a different kind of fail on production, but it sounds useful(yeah, and pretty cool) nonetheless.
You want to purchase a large quantity of licenses, and you want a discount for them. So you ask for just one and use it as a proxy to know if the Company is flexible in its pricing? Is this standard practice?
I must say that I was at a company where the purchasing guy was always asking for discounts up front. He often tried to deceive the salesmen (for example he asked for free ISDN-GSM gateways to a telecom guy who ignored its price and thought they would cost like a phone). For him it was "just bussiness" and the way it's played the game.
Were we a toxic customer? For the naivest of our providers, sure we were.
Anyway, I'm doing it with my two years and half son. He loves it and helps him to relax and rest(he's very active).