216 karma · joined May 19, 2015
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.
So:
:o <C-r>%<C-w>new-filename<ret>
Would open a new buffer at /path/to/the/previous/buffer/new-filename. The file isn’t created on disk until you explicitly write, so :w! to save the first time.
If you literally just wanted to create a new file instead of opening a buffer, you could do that from inside Helix with :run-shell-command (aliases sh or !) instead of another terminal:
:sh touch <C-r>%<C-w>new-filename<ret>
The :o method has the advantage of LSP integration. For example, when I create a new .clj file that way in a Clojure project, the new buffer is pre-populated with the appropriate (ns) form, preselected for easy deletion if I didn’t want it.
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.
I guess they anticipate users hitting escape a lot. Making it a large target doesn’t strike me as a worse use of the space than dividing function keys into blocks of 4, and more likely to be intentional than an artefact of generative AI.
[0] https://www.linkedin.com/feed/update/urn:li:activity:7353029...
We could presumably infer it still wasn’t “missing” as recently as a thousand years ago from later sources referring to it, even if the specific text (or oral tradition) those authors knew of hasn’t survived.
Like how we know about some of now lost Greek plays, originally written in the 5th century BC, because they were still being performed in Imperial Rome and writers of that time described them, even the details of how they were staged.
That way you only have to look at it when you need it, and you can also figure out what you were doing last week/month/year if necessary.
They’re just regular OpenType files, albeit with “beware of the leopard” levels of filesystem obfuscation, so it’s fairly trivial to divorce them from Creative Cloud’s control if you want/need to.
And on the web, Typekit is just CSS and woff(2), so again, no (technical) impediment to doing whatever you want with them.
The gif at the top doesn’t demonstrate everything included. From the text:
“There are currently three variations: bars, dots, and dot-lines (line charts with tiny dots at the joints between segments), each of which has five weight variants.”
See also their examples page: https://beta.observablehq.com/@tomgp/after-the-flood-i-spark...
I’d call delivery as ligatures a trade-off. Much easier to make it scale with text on the web when embedded inline, it’ll match the text colour for free, and the underlying numeric data are trivially retrievable and machine-readable. Compare the example on the Sparkline wikipedia page, which don’t scale with the text and are almost invisible when using their own dark mode.
user=> (doc clojure.core)
-------------------------
clojure.core
Fundamental library of the Clojure language
user=> (doc +)
-------------------------
clojure.core/+
([] [x] [x y] [x y & more])
Returns the sum of nums. (+) returns 0. Does not auto-promote
longs, will throw on overflow. See also: +'
user=> (source +)
(defn +
"Returns the sum of nums. (+) returns 0. Does not auto-promote
longs, will throw on overflow. See also: +'"
{:inline (nary-inline 'add 'unchecked_add)
:inline-arities >1?
:added "1.2"}
([] 0)
([x] (cast Number x))
([x y] (. clojure.lang.Numbers (add x y)))
([x y & more]
(reduce1 + (+ x y) more)))But it’s a niche (competitive gamers and mechanical keyboard enthusiasts) with deep pockets, to whom “buying a new keyboard” is basically no barrier at all.
Probably the most practical DIY option.
A Hall effect sensor works by running a constant current in one direction while measuring the potential difference in a different axis. The keyboard’s PCB needs to be able to register a range of values, not simply binary on-off. Regular keyboards aren’t equipped to do that.
Typically in an HE keyboard, the sensors are mounted to the PCB. The “switch” itself is just a neodymium magnet at the end of a POM stem, in a polycarbonate housing with a spring.
There are other kinds of magnetic switch that have historically been used in keyboards – e.g. Fujitsu used reed switches in the 70s – and in theory you could probably build them into a Cherry MX-compatible package. But they wouldn’t provide many of the benefits of HE keyboards, besides smoothness and reliability, and I’m not aware of anyone doing it.
Being contactless, they’re extremely smooth, quiet and reliable, and being able to set the actuation point exactly where you want it is a very nice bonus.
I’ve been using a Monsgeek M1 HE (I think probably still the cheapest option on the market, even though it’s an incredibly solid block of aluminium) since the summer, mostly just for coding, and for me it’s the best keyboard I’ve ever used.
If your preference is for tactile/clicky switches, or heavier linear switches that you hit hard enough to bottom out, or you’re perfectly happy with any old membrane keyboard, it’s probably not worth the expense.
Atmospheric/pneumatic railways were still a popular idea in the mid 19th century. The Dalkey and Paris – St Germain atmospheric railways had each had over a decade of service before closure in the 20 years before Chalmers’ patent. They obviously had their own, considerable issues, but would have reduced the ventilation requirement.
I think there’s one collection of _The Order_ so far (“Die Mensch Maschine”, print and digital), beyond that you currently need the individual Progs. I’m pretty sure they are all available digitally, but it’s not cheap or convenient.
But all of _Nikolai Dante_ has been collected (print and digital), there’s a digital _The Bendatti Vendetta_ graphic novel, most of his Dredd work is probably available scattered across various collections…
Instead of trades, a lot of shorter/less popular 2000AD series are reprinted in full in the back of the monthly Judge Dredd Magazine – the complete _Angel Zero_ is in Meg 370, for example.
A. Actually I made a mistake with that 20,000 lines of code statement – that was just off the top of my head. I need to correct that if I can figure out how, but it also depends a bit on what lines of code you count. The original 30-year-old C program is 325 lines, and the “patch” file for the synthesizer was 298 more lines. I guess it just felt like 20,000 lines when I did it.
Given that it was written and debugged in 4 days, I can’t claim the programming chops to make 20,000 lines of working code that quickly. But, to synthesize it in real time, in 1983, took 2 years to design and build a 19” rack full of digital hardware and 200,000 lines of system code to run the synthesizer. All that was already done, so I was building on a large foundation of audio processing horsepower, both hardware and software. Consequently, a mere 325 lines of C code and 298 lines of audio patching setup for the 30 voices was enough to invoke the audio horsepower to make the piece.
https://cdm.link/2015/04/thx-deep-note-creator-remade-iconic...
The unpleasant side-effect of this approach is that anyone using a screen reader for accessibility reasons is told to consider switching it off so they can look at the font the author picked.
But they are also offering paid support plans for xtdb: https://www.xtdb.com/support/production