328 karma · joined July 31, 2011
And I guess it will only be a matter of time before robots will start doing this too, so please don't tell anyone ;-)
di = diff
dc = diff --cached
ap = add -p
unstage = reset HEAD -p
discard = checkout -p
ci = commit -v
ca = commit -va
amend = commit -v --amend
reword = commit -v --amend --only
extend = commit -v --amend --no-edit
ri = rebase -i
rem = rebase master
rim = rebase -i master
red = rebase development
rid = rebase -i development
continue = rebase --continue
skip = rebase --skip
pu = push -v --progress
poof = push -v --progress --force-with-lease
pusu = -c push.default=current push -v --progress --set-upstreamWhy is that bad? It's a huge waste of effort, increases the burden on anyone who's maintaining a package using those micro-libraries, and will guarantee more unpatched security vulnerabilities and unmaintained packages in the long run.
Hoping technology will save us is as foolish as believing Jesus will, both extremes are bad and missing the larger point that humans are far more complicated than we like to admit.
But Elm is actually moving in that direction, the last release added a process abstraction inspired by Elixir, and I've read they're even considering BEAM as a compile target, in addition to the current JS target and plans for a WebAssembly target.
Sure, things like WebSockets are changing this, but you don't really need an event loop if you have proper threads or a multi-process server (you know, like Node clustering, which you tend to need anyway once you outgrow the limits and pains of a single event loop).
I came here through the RSS feed, and likely would have ignored it without the "Google" mention.