694 karma · joined June 17, 2013
I'm actually surprised at the naivety of whoever wrote this. I'm not an op at all and I understood enough about ShellShock to know that this isn't correct at all.
[1] https://facebook.github.io/react/blog/2015/01/27/react-v0.13...
"I was hoping we could make a rifle out. Never mind."
"Yeah, review that shit . . . Why didn’t he say possible child, why are they so quick to call fucking kids but not to call shit a rifle."
Even I have to refresh my memory on these ambiguous parts of the language from time to time.
Express: no
Neo4J: rather not
Node: fuck no
My point: your opinion is exactly that... everyone has their own, and it's as useless as mine, in these comments, until you add some weight behind it.
Yes: "using a computer that tried more than 300 billion plaintext guesses every second"
The Arabic version was obtained by doing an educated guess based on the English version
The Zen of Python:
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!It really annoys me that I spent 4 years studying this to find that other people who scrape together snippets of JavaScript & PHP feel entitled to call themselves an "engineer".