mclehman

I'm struggling to come up with anything other than "Cody".

I wish I'd done that with a lot of the indie music and otherwise unpopular things I was interested in years ago. There's a particular album I wish I could find and listen to, but I've only ever been able to find one article talking about it, all links dead, and that itself was long enough ago that I've forgotten the name of the album and band.

I had a lot of things saved through Instapaper right from its inception, but I stopped using it regularly and one day when I went back I didn't appear to have anything saved anymore.

Since then, I've been much quicker to download things I might want in the future. Storage is cheap, archaeological effort is not.

Piling on with a bit more pedantry, my experience is a bit different.

In my current ring theory course, we have indeed written things like 3 * 3 = 1 when working in |F_5 (not sure that notation is going to work as well as I hope, looks alright in the app I use), but it's not the equality symbol is overloaded, but the numbers themselves. Rather than using = to mean numeric equality and equality w.r.t. equivalence classes, we just use the numbers themselves as shorthand for their equivalence classes.

I'm in much the same boat: Planck with the Workman layout (laptop and desktop), laptop keyboard with both Workman (touch typing) and qwerty (very much not touch typing), and on-screen on my phone.

Even just swapping between the staggered and grid layouts, both Workman, changes how I type in a way that I'm reasonably confident would affect the accuracy of this service.

Agreed, breaking your concentration to type is bad and rather easily mitigated. However, the time required to break the flow of whatever you happen to be doing is very small.

Imagine you could type instantly. As soon as you thought of what you wanted to type, it was there. Moving a block of code or an expression into a REPL and evaluating it would be immediate. The first bit of boilerplate for a new project wouldn't get in the way of thinking about what you're actually working on. None of your time would be spent on the mechanics of transcribing.

Is it a minor optimization? Definitely, especially given the real limits on human tying speed, but anything that keeps you in the zone is going to add up over time. In my opinion, it's not that typing is a bottleneck, it's that breaking concentration for anything is one of several bottlenecks.

Edited to add: As I think about it, I may have failed to draw a clear distinction between "breaking concentration to type" and "breaking the flow", and in fact went back and forth on the wording I used to refer to each.

To summarize, I feel that breaking the flow can happen anytime you have to wait on something, be it physically typing a command or bit of code, waiting on compilation or evaluation, or glancing up at and thinking about a notification. Build times are largely out of your hands and people will always interrupt you (in person if you mute notifications), but physical typing delays are solely in your own hands and eliminating them can help keep you in the productive flow.

> All the Chinese people I meet here are working.

To be fair, you wouldn't see Chinese individuals "unoccupying" units.

I wouldn't characterize "stole from" as a transitive relation.

If I recall correctly, someone was able to fool TouchID a few years ago using a fake print created purely from pictures of a German government official.

There is also a very large range of responses to the EnChroma glasses. I've seen or heard about plenty of intense reactions to them, but my personal experience has not reflected that.

My brother-in-law and I are both colorblind (mine is not as severe as his) and he bought a pair a few years ago. He enjoys the difference but not enough to wear them consistently, and they had a barely perceptible effect on my own vision, just giving green a bit more "pop".

I think the main issue is that it's easy to group all colorblindness together even though "huh, I guess my shirt really is purple" is very different from "I look at streetlight positions, not colors."

That said, even my mild colorblindness puts me at a massive disadvantage on certain Halo maps or against certain team colors. In situations like that, I might as well be fully colorblind asI end up having to play based on movement alone.

Would this be similar to the eSIM in my Pixel 2 XL?

Sure, you can flatten that example, but I'd still be interested in losing the explicit and repetitive null checks.

Albuquerque born and raised, I use up for north and east for the same reason.

Everyone else I've asked in ABQ uses up for "the direction I'm going".

Personally, I just keep scaling up the springs in my switches. Started standard, then went up to 85g, sitting at 180g with 250g switches waiting to be put into a board. No gentle typing required and I never bottom out strongly while typing.

What WiFi problems would those be? I'm sitting on Sierra for now, but my laptop has been refusing to connect to a network automatically 95% of the time on wake. Now I'm wondering if it's worth braving High Sierra for a fix to it.

This issue is one of the things Perl 6 addresses well in my opinion.

Regular ranges include their endpoints, and you can think of ^ as "not including" or "up to (exclusive)"

1..5 is 1, 2, 3, 4, 5

1..^5 is 1, 2, 3, 4

1^..5 is 2, 3, 4, 5

1^..^5 is 2, 3, 4

There's also convenient shorthand for 0..^n (useful if you want to do something n times): ^n

In that case, why have the quick access menu at all?

That said, brian d foy is not Brian D Foy.

Interesting. I use Workman as well on my 40% keyboards (standard keyboards I use QWERTY and don't even attempt to touch type). I think learning Workman and Vim at the same time is what saved me.

I never remapped anything, I just avoid h/j/k/l (I have my arrow keys bound to the homerow) and added a bunch of bindings (F3-8, for example) that wouldn't normally be of much use to me (sitting behind the fn key on my laptop) but are also homerow-accessible.

I have transitioned to emacs + evil lately, and found that mostly seamless, but I can imagine it would have been rough if I was trying to keep QWERTY muscle memory.

Easier to write, yes, but only outside of emacs (and anything with good snippet support). Within emacs, <s TAB expands to

  #+BEGIN_SRC |
  
  #+END_SRC 

with the cursor placed to specify a language.

As for readability, I don't think it's clear at all that ```...``` beats

  #+BEGIN_SRC perl
  ...
  #+END_SRC

* * *

As it turns out, I hadn't refreshed the page for hours, and someone else said pretty much the same five hours before.

Agreed. Straightforward arithmetic is the capability, in Lisps represented in such a way as to fit with the philosophy of the language.

It's not like the majority* of languages see infix (or prefix, postfix, postcircumfix, etc.) notation as a basic enough concept to allow defined functions to make use of it. Arithmetic always seems to be the special case. No operator overloading, but arithmetic is pre-overloaded. Parentheses of function calls are all you need to keep track of subexpressions, but arithmetic will have an arbitrary and large list of precedences.

*correct me if I'm wrong. I know a fair few languages but mostly deep dives into particular niches. That could bias me.

Decred is currently mined using a mix of PoW and PoS.

Current supply[1]:

PoW-mined: 43.5% PoS-mined: 21.8% Development Subsidy: 7.3% Airdrop: 13.7% Dev Premine: 13.7%

Blackcoin is also PoS mined, and NXT reaches consensus using PoS but if IIUC is not mined per se.

1: https://www.decred.org/

I agree with that. You can hand limits as a tool to someone already comfortable with the concepts and present them as a way to quantify their intuitive understanding.

Lisp + Emacs + SLIME: miss no longer.

Picking them all up is a tall order though.

I've used the Radeon control panel. I also use the Slack and Spotify apps all the time with no complaints.

The Radeon interface does not fit in at all with Windows (nor macOS or any Linux DE I've ever seen, for that matter) and is almost always glitchy for me.

/r/mechanicalkeyboards, /r/fountainpens, /r/headphones and a lot of programming language subreddits are usually friendly.

Perhaps they meant to make a distinction between the inherently debatable "what he would have wanted" and "what we actually have a written statement of him wanting"?

I for one use not just an exotic layout, but a homegrown one. My alphas match the Workman layout, and I use a 12 column, 4 row keyboard (a Planck form OLKB) so that I have plenty of thumb keys.

Symbols are kept on a separate layer of keys alongside a numpad, so that they can be grouped by how I use them. Parens, brackets, braces, are all in the two leftmost alpha columns. I keep $, @, and % in a column because I use Perl fairly often. I also keep # and ! together for fun.

Now, I'm not saying it's particularly common, but I have a friend with a similarly exotic setup and we use them on a daily basis.

> I don't think that keyboard part is really meaningful to anyone who claims to love programming

I'd beg to differ on that front.

Have you looked at Perl 6 at all? Whitespace in regexen is insignificant if not quoted, so not only can you add a little space between sections, you can split a regex over several lines and add comments throughout.

It also has first-class grammars, so you're less tempted to reach for regex when something more powerful would help.

I tried Vim bindings in Atom for about five minutes before the inconsistencies pushed me back to regular Vim (this was back when I started learning).

I switched to emacs/evil-mode a while ago (maybe 7-8 months into using Vim) and I've really enjoyed it. Evil does everything I want (at least that I know I want). There are unsupported features, but not ones I'm familiar with.

Text objects are supported and the ports of commentary and surround have worked great as well. Marks and macros are fully supported.

I much prefer emacs-style remapping, and there is a package, vim-leader, that gives you a nice way to define leader mappings.

I can't speak for :g// (don't really use it and on a phone at the moment so I can't check) but :s// works well.

My overall opinion is that vim-style editing is second to only rolling your own modal editing style (there is an emacs package that lets you do that, I believe) and that emacs as a host editor for that editing is hard to best as well. To be fair, I'm a really big fan of Lisp, so that's also part of the draw for me. Magit is something else to try out as well. In my opinion, it's much better than fugitive.