llIIllIIllIIl & runako give me an email on steven[at]build.io and I'll share. As mentioned, we stripped the site back while we overhaul and we certainly didn't expect this today!
To be clear, you just answered "Do you care to show prices?" with No.
Readit Newsnaniwaduni commented on An Update on Heroku heroku.com/blog/an-update... · Posted by u/lstoll
"We know changes like this can raise questions, and we want to be clear about what this means for customers."
Proceeds to not be clear about what this means for customers.
Oh, they're very clear, just not explicit.
naniwaduni commented on A case study in PDF forensics: The Epstein PDFs pdfa.org/a-case-study-in-... · Posted by u/DuffJohnson
I know I'm not the brightest bulb by any measure, but do some people really take less than at least a few minutes to come up with one-liners for problems as novel as graphical transformations to PDFs? Maybe if the presumed techie hacker / federal worker took it as an amusing challenge I could see this being done, but genuinely out of pure laziness? That's incredible if true.
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.
naniwaduni commented on The world of Japanese snack bars bbc.com/travel/article/20... · Posted by u/rmason
You could play with that though since "both sexes" could be perceived as "both individuals that have a sex" and "husband and wife" don't have any technical meaning.
I'm not a lawyer, but they're working on it.
There is value in maintaining the fiction that words mean things.
Deleted Comment
naniwaduni commented on Always bet on text (2014) graydon2.dreamwidth.org/1... · Posted by u/jesseduffield
This reminds me that I just learned the other day that .a files are unix archives, which have a textual representation (and if all the bundled files are textual, there's no binary information in the bundle). I thought .a was just for static libraries for the longest time, and had no idea that it was actually an old archive format.
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!
naniwaduni commented on Always bet on text (2014) graydon2.dreamwidth.org/1... · Posted by u/jesseduffield
> For the negligible added CPU cost of deserialization, you completely lose human readability.
You could turn that around & say that, for the negligible human cost of using a tool to read the messages, your entire system becomes slower.
After all, as soon as you gzip your JSON, it ceases to be human-readable. Now you have to un-gzip it first. Piping a message through a command to read it is not actually such a big deal.
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.
naniwaduni commented on Japan to revise romanization rules for first time in 70 years japantimes.co.jp/news/202... · Posted by u/rgovostes
A typical example for English is the adjective order.
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.
naniwaduni commented on Japan to revise romanization rules for first time in 70 years japantimes.co.jp/news/202... · Posted by u/rgovostes
How? Near enough no one was using the Kunrei system for any of that. If anything this will make it more consistent or at least no worse. Macrons are the biggest inconsistency but that’s always been the case.
It was either Hepburn, the English title (i.e. rock instead of rokku), or just most sensibly kana/kanji that would have been used for this everywhere, never other romanisation systems, to within a rounding error.
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.
naniwaduni commented on Japan to revise romanization rules for first time in 70 years japantimes.co.jp/news/202... · Posted by u/rgovostes
Politics aside, Hepburn is better. You can’t seriously say you prefer “konniti-ha” and “susi-wo tabemasu”
You are very, very likely to find people who prefer "sushi wo tabemasu", because standards are great.