Out of the box, there’s zero security or audit trail. Building that properly isn’t trivial and, even with it in place, many corporate infosec teams would have fits if you suggested that engineers can make arbitrary inspections/modifications to a running production system.

Where it could be appropriate, often you’re running the code in autoscaling containers or something similar. Modifying one instance then is rarely anything but a terrible idea.

Where I have used it is for things like long-running internal batch systems that run a single instance and never touch any sensitive data. Connecting a REPL in those cases is much more flexible and powerful than, say, building a dashboard UI or a control API over http, and you get it for free.

[0]: https://reederapp.com

[1]: https://1password.com

[2]: https://github.com/quoid/userscripts

Kovid documented his rationale at some length here: https://github.com/kovidgoyal/kitty/issues/33

  :insert-output Run shell command, inserting output before each selection.
  :append-output Run shell command, appending output after each selection.
  :pipe, :| Pipe each selection to the shell command.
  :pipe-to Pipe each selection to the shell command, ignoring output.
  :run-shell-command, :sh, :! Run a shell command

I’m not sure if replicating Sublime’s Ctrl + D is possible or not, but there are other ways to achieve every use case for it I can immediately think of. e.g. I think I’d typically be doing `h` to select every instance of the symbol under the cursor, or using `s`elect to reduce a selection to a match, possibly yanked and pasted.

If your new hire is a British or Irish citizen, you ask for their passport on their first day and retain a photo/scan. In most cases this means that a layperson has to verify that the (possibly foreign) document is genuine, but I don’t think fake passports are a statistically meaningful problem.

If they have a visa or, probably most likely in recent years, EU right to remain, they will have a share code for online verification. That takes you to a page with their details and a passport-style photo that you can download as PDF for your records.

Identifying whether someone has the right to work has never been a problem. If somebody is working illegally, it’s because the employer is either knowingly employing them illegally, or doesn’t care/bother to check (or even know that they’re legally required to do so – a perennial problem with early stage startups in London, in my experience).

Helix on the left and a Clojure repl at top-right in terminal panes. Portal data viewer in a browser pane at bottom-right.

Try btop, a resource monitor with true colour support and 37 builtin themes.

Even if macOS wasn’t UNIX-certified, Apple would still be unwilling/unable to include the GNU software due to the license. I can’t see the Apple of today implementing a full suite of non-GNU software but with GNU-style options either.

So, POSIX compliant or not, there’s probably no world where `grep -P` works out of the box on a Mac.

Isn’t it rather that Darwin was based on BSD 4.4? I’d imagine GPL 3.0 is a bigger impediment to them ever migrating to GNU tools than any desire to be UNIX certified.

The “missing” keys are on additional layers reached via a modifier key, or by overloading keys on tap/hold, or by increasingly esoteric methods the smaller the board gets: chording, tap dance, etc. They’re typically no less accessible than capital letters, while allowing you to keep your fingers on the home row.

For me, the additional keys on my larger keyboards rarely prove useful in practice. I end up mostly using the same subset available on the 60% I’m typing on now – it’s quicker and more comfortable than reaching over to the dedicated key.

Consider also that it was developed in the 20s and 30s. Nowadays you could throw some moderately hefty compute at almost everything of note written in the English language and come back to an error-free analysis after lunch, but who knows how representative was the corpus they analysed, painstakingly and manually. It might have made perfect sense with their data set.

Ultimately, the English language didn’t evolve to be easy to type, there will always be compromises somewhere, and the English of today isn’t the English of a century ago anyway. I imagine you’d get quite a different layout if you based it on Gen Z text messages or something.

Personally, I can’t help but note that Dvorak’s first name was August.

(Typewriting Behavior, for the curious: https://archive.org/details/in.ernet.dli.2015.74878/page/n11...)

STM, atoms and agents were there from the beginning. I think futures and promises were added in 1.1. core.async is from 2013. Even popular third-party libraries like promesa and manifold are around 10 years old at this point.

I think flow promises to make it easier to orchestrate core.async, specifically, in complex applications, but the essential primitives are far from new and I don’t consider them any harder to use than JavaScript.