The legal system does nothing to fix the harm done by murder to the person who's now dead, either.

The Latin alphabet variant modern English uses has uses only ~11 kinds of strokes, where is this 26 coming from?

An alphabet assigns a letter to a sound. No more no less. English no longer has an alphabet because the Latin alphabet, designed for Latin languages, replaced the native Runic alphabet.

Serbian has an alphabet, as does Italian. All other European languages I'm aware of don't.

Interesting! So what’s the abc’s we learn then?

Arbitrariness of the sign is a principle that requires so many epicycles to present as "true" that it's more of a warning against overgeneralization than an insight with any significant predictive power in its own right.

Let's call the arbitrariness of the sign, blinga. Why do you think blinga requires "epicycles"? Blinga makes pretty modest claims: there is no requirement that the form of a sign matches that which it signifies in any way.

Nearly all the security value of 1fa is that it keeps your users from picking the own passwords.

From ChangeLog:

    * telnetd/utility.c (getterminaltype): Change the
      name `user_name' to `uname', as the former shadows a precious
     and global variable name.

global variables are public enemy number one

Congratulations! Now you've got yourself a precious and global(ly exploitable) vulnerability...

> and the people worried about this aren't the ones bringing the real revenue.

It's this one. If you're in a position to refund a "cost accident", then clearly you don't have to enforce cost controls in real time, and the problem becomes much easier to achieve at billing cycle granularity; the user setting a cost limit is generally doesn't care if you're a bit late to best-effort throttle them.

To be clear, you just answered "Do you care to show prices?" with No.

You’re right - reading that back, it comes across as a “no,” and that wasn’t my intent.

We should show pricing, and we will. We temporarily stripped the site back while overhauling positioning and pricing, which is why it’s missing right now. That’s on us, not a stance against transparency.

In the meantime, I’m more than happy to share pricing directly.

At a high level on our pricing: - Current customers are on a mix of usage-based and fixed monthly plans, depending on their needs. We've found many of our customers love the fixed plan as it's a whole new level of predictability. - We’re generally architected to land well below Heroku’s Enterprise pricing and to be competitive with a IaaS. - We want pricing to get out of your way as you scale, so no big steps in pricing as you add services. - Databases are HA by default and support replication. - Pipelines and review apps don’t require hacks to avoid per-review-app database costs.

Happy to answer specifics here or over email if helpful.

Oh, they're very clear, just not explicit.

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.