pwdisswordfishq

So much trouble to avoid introducing the optional monad.

> Knowing nothing about it this particular movement, the main danger I foresee is essentially hubris.

One of them selfawarewolves.

For a second I was hoping that the bubble was already bursting.

This just shows the command line was badly designed to begin with.

If CLI programs received already-opened file handles instead of pathname strings, most programs would have no need to have the concept of a "current directory" at all. It could be something purely internal to the command-line shell.

It would also be more fitting for a capability-based OS instead of one where every program has an ambient permission to access anything in the whole file system.

It does not last, though

Though in this case, it would be: escape, don't sanitize. "Parse, don't validate" applies to taking inputs; this is about generating outputs (like SQL queries or HTML markup).

Why not both?

As we all know, beginners love Emacs keystrokes.

> Every day, Wikipedia biographies of living people are flagged for deletion because the subjects are not “notable” enough. How do these poor souls take the news?

How entitled must one be to assume they are owed a page in Wikipedia?

Indeed, my first thought upon seeing the premise explained was "I would have chosen a different philosopher".

> C++ on the other hand is highly opinionated, [...]

> A lot of the C++ community doesn't use these features

That they even have the possibility shows how un-opinionated C++ is.

> The 1g object is more dangerous because it's able to actually pierce you.

Why?

It surprises me it was even implemented.

Because restaurants don't want businesses like DoorFash to scrape it.

I would take a page refresh that takes two seconds over waiting half a minute for a page to "hydrate"