339 karma · joined July 4, 2012
I tried binding the arrow keys first, but it turns out I sometimes give up in the middle of writing a command in favor of reusing one from recent history, for which I need the original arrow bindings.
The only thing that interests me on Facebook is what my "friends" have originated. My interest and time spent have declined in direct correlation with the amount of said content.
Seriously, though; we all use the same (couple of different brands of) phones to connect to the same (couple of different brands of) station hardware to get through to the same global network. A small difference in the choice of stations shouldn't make a large difference in the amount of cost reflected.
This. If I may reiterate your point:
`is_foolike(x)` may not be much better than `x.startswith("foo")` but, say, `is_superuser(x)` is much easier to understand than `x.username.starts_with("su_")`. And note how the mental burden is decreased in this case as well, as a first-time reader would not be wondering why we're checking usernames in the middle of a function way past login.
The only difference was that the second, wiped phone was an empty "dev" phone, thankfully. It then caused Apple to ask for a series of upgrades to develop for, starting with XCode and ending with my MacBook Pro.
"foo1 on the first iteration, foo2 on the second, etc."
As much as I am a fun of weird little endeavors like programmatically modifying the local scope, my answer is usually along the lines of "...arrays."
I watched the talk a couple of times and went through earlier versions of the code -- but I'm not fluent enough in Rust to separate idiomatic Rust code from actor model code.
Great job and great talk, theanzelm!
start-daemon && configure-daemon-while-running && stop-daemon
The point is, I've seen far more && than RUN directives so the decision was backwards.
How, may I ask? I've been looking for a good way to do this for a long time; nowadays I'm using a checklist and AMIs on AWS.
Ansible is too damn slow, does not know how config files work and clutters the terminal/my home directory/my known_hosts.
Dockerfile is a badly written shell script using && instead of errexit.
Combined with the power of Chinese PCB manufacturers (smart-prototyping in my case), my childhood dream of "making my own PCB one day" was realized pretty easily.
I honestly think people prefer spaces because it's hard to get the above right. With spaces, if it looks right, it is right.
(Wow, I can't believe I just argued in favor of spaces.)
I'm a tab person myself. With tabs, those 2-space-loving perverts have no power over me!
> And this is wrong -- this is not how Python if statements work.
Huh? Didn't you yourself say I was not talking about if statements:
> What you are talking about is a different kind of expression, similar to a ternary operator. It is not the same as if...else
In any case, I'm talking about the case that goes `TRUE-CASE if COND else FALSE-CASE`, as can be deduced from my typing `TRUE-CASE if COND else FALSE-CASE`.
> Could you elaborate on that?
It's a very opinionated statement on my part. `if COND then TRUE-CASE else FALSE-CASE` is the correct form to use, in my opinion. Python uses `TRUE-CASE if COND else FALSE-CASE`.
On the other hand, you have a concept which translates easily to any language with first-class functions and lambdas. Even the syntax stays the same among languages which use "f(x,y)" for function evaluation and parameter passing.
/* This post is for those occasions when a list comprehension style is advocated over a functional style, which I know was not necessarily what you were doing in your comment. But I think the two points are valid enough on their own. */
Um, why would you break (or rather worse, invert) such a common convention?
> So 11 is 9+3–1.
...and not follow through, just two sentences later?
> [...] at which point the number 11 would be 2-0-1 (1+1+9).
Surely you mean 2+0+9 or 9+0+2?
And it is right that the fate is in the author's hands. It's those hands that we are trying to tame.
> Hmm? I don't see any such PR.
Hmm, neither do I.
The "Retronator Magazine" banner at the top and the nag banner at the bottom take up too much of the vertical space and combine with the width of the text column to make my viewport essentially square. Add to this the ultra-wide 1920+ pixel images that run past the edges of my screen (and are three times as wide as the text), and it should be obvious why I felt I was reading an excellent article through a toilet paper tube.
Firefox and Chromium at 1920x1080, and sorry I couldn't do this article justice.
12,000 years... Older than our planet, according to Young Earth creationism.