naniwaduni

It's not a novel problem. But yes, I don't think people quite appreciate how quick and easy it is for people who are in the habit of brewing up one-liners to solve simple problems to do that. I've done it here on HN for jq toy problems before, and I don't really doubt there are people similarly familiar with imagemagick.

There is value in maintaining the fiction that words mean things.

It may amuse you to learn that tar headers are designed as straight up text tables with fixed-width columns, marred only by the fact that modern implementations pad with 0s instead of spaces. The numbers are encoded as octal digits!

The human cost becomes negligible once the tooling is already integrated. You don't get to call it negligible until after the integration has been done.

Adjective order in English is basically that most essential qualities of the object go closest to the head. There are lists out there that try to break this down into categories of adjective ("opinion-size-age-shape-colour-origin-material-purpose"), and to some extent the anglo intuitions on which sorts of properties are more or less essential are not trivial, but it's not as arbitrary as people want to make it out to be.

It was almost never quite Hepburn either, usually shi/chi/tsu/fu/ji with no di/du, but often alongside wo/he/ha (in roughly that order of likelihood, not always consistently), macrons almost never, っち is cch. Ironically, I have to imagine there's more "bastardized Nihonsiki" out there than "bastardized Kunreisiki", because the differences between the two are exactly the ones that matter when typing them out, and of course everyone in the j/e scenes is by far most often inputting wa-puro ro-maji (and of course that's ji, not zi, because which one is on the home row?).

In short, the usual infelicities of Japanese romanization as practiced in the wild on keyboards people actually have, and there is a method to the madness but it's not what any of the standards reflect.

You are very, very likely to find people who prefer "sushi wo tabemasu", because standards are great.

The terms of the licenses have legal bearing. The definitions of open source are a historical accident that mostly traces back to "well GPLv2 already exists".

The headline status doesn't have to be "worst of all systems". Pick a key indicator, and as long as it doesn't look like it's all green regardless of whether you're up or down, users will imagine that "green headline, red subsystems" means whatever they're observing, even if that makes the status display utterly uninterpretable from an outside perspective.

"Coward" is really not the kind of word that admits "very simple definitions" that people can agree on, no.

One of the dirty secrets is that you don't need to back up confidence to sell it if you don't plan to be around when it falls apart.

1357 (2014-04-18) is pretty bad.

(Bonus points for the alt-text argument being isomorphic to nothing-to-hide.)

You're right, "journalists don't have a world model and can't compare what they're saying to anything" explains a lot.

All of them, pretty much.

Your program can be executed with fds 0-1023 already open.

A stark reminder that all operations on strings are wrong.

4 instalments spaced by 2 weeks with the first up-front averages out to about a 3-week float, which is less than the grace period on ordinary consumer credit cards in the US. And Klarna charges merchants more for this!

The fact that the author has never actually bought a taco with Klarna pretty clearly detracts from the article, even, in that they really don't seem to have any idea how the other half interacts with financial services.

Option-hyphen usually produces an en dash—the em dash is on option-shift-hyphen.

The Unicode horizontal ellipsis is an abomination that doesn't belong in English prose, though.

It'll only be permissible for foreign governments to influence your media moguls to influence your youth on their behalf?

The way I learned it, swap is basically the inverse of file caching: in much the way that extra memory can be used to cache more frequently-used files, then evicted when a "better" use for that memory comes around; swap can be used to save rarely-used anonymous memory so that you can "evict" them when there are other things you'd rather have in memory, then pull them back into memory if they ever become relevant again.

Or to look at it from another perspective... it lets you reclaim unprovable memory leaks.

Well, I guess it's helping to distinguish authors who are doing arithmetic they understand from ones who are copying received incantations around...

You really just very rarely want codepoint indexing. A byte index is totally fine for view slices.

> As you might expect, Generation Z adults (ages 18-28) receive more financial support from their parents than their Millennial counterparts (ages 29-44),

I mean, yeah, something like a third the former are college students! What a trash fire of an article.

I tossed pathogen in favor of git submodules in ~/.vim/pack/*/start/ in 2017 and it's still like that.

We do have, like, four versions of that in the US alone, yes, starting with 529 plans.

Keep it simple, standard,

I'm not sure that is ironic.

The polyfill is a distraction; it does nothing for the use cases in the wild unless it's shipped with the browser, which is basically orthogonal to the spec and in any case Chrome was not willing to do.

It's something that people keep reinventing on both sides of the connection. That XSLT is the better of two terrible ways to do it, and that you're making the argument that the other one still exists, is an embarrassment.