wpollock

> It being Halloween yesterday ...

This comment was made on October 30th. So "yesterday" was the 29th. Where in the world is Halloween on the 29th? I thought it was on October 31st throughout the world.

> There are no book bans in the US. ...

Not true here in Florida. The governor banned and burned books that taught slavery was bad, revoked tenure and fired all teachers who were reported teaching that slavery was bad. The new state-approved textbooks teach that slavery taught blacks useful skills and that there was violence on both sides.

I sometimes wonder if Kubernetes was designed with selling support and training services as a goal.

While I understand why C++ defines bool as an Integer, it might have been better if it wasn't. It's not a problem for me that in some modern languages, boolean cannot be mixed with numbers in an expression.

Is "fearless concurrency" a technical term? I thought it was just the catchy name of a chapter of the Rust book.

I too love plain text data, but absent a universally accepted standard, meta data is needed to avoid guessing a document's charset, encoding, and line ending convention.

Associating such meta data with text files wasn't simple in the beginning, but that changed in the 1990s. Nearly all filesystems since then allow meta data: POSIX compliant filesystems support extended attributes, mostly used for security meta data. Even ancient HFS (Apple Mac) supports meta data. NTFS supports it with alternative file streams.

While possible, no system I know of attempts to use any such meta data, probably due to a lack of standards. A pity.

I think the best shape for a city is a Mobius strip: go anywhere without turns, so no traffic lights needed.

Dang says tomhow is the better moderator.

Dang, says tomhow, is the better moderator.

WiFi is not an acronym for "wireless fidelity"; the developers likely just thought it sounded cool. The term is probably just a play on the words from the audio term "high fidelity". The phrase "Wireless Fidelity" is meaningless.

The more you know!

> The website should display a qr code you can scan with your phone that allows you to then login...

A malicious website can display a QR code too. I think this "feature" could cause some of the security issues that passkesys were intended to solve.

I use Keepass and the free tier of Dropbox, to keep my passwords strong and available across multiple devices. (Dropbox not required, you can store the database on a thumb drive.) Backups are no problem.

Keepass (or KeepassXC) stores other data as well, including the correct URLs for sites. So my workflow is simply to click the URL from within Keepass, copy the username and password, and paste them into the login screen. So easy even an adult can do it! (Humor attempt)

For convenience, Keepass database can be unlocked with either a password or biometrics (your fingerprint).

(Not affiliated with Keepass, just a happy longtime user.)

Two suggestions, based on my experience:

1) Add a section called "Potential Changes". This is broader than "missing features", and can include other items too, such as new hardware that might become avaliable, customer requirement changes you might anticipate, possible new technology (e.g. a new database or cloud service that might be useful), multilingual support, etc. Listing some of these often causes reviewers to think of others as well.

Ensuring the design is modular around such changes means implementing any of them will be far easier than if assumptions are hard-coded throughout the codebase.

2) Security and privacy are two aspects of a more general category of "compliance assurance". Those two are worthy of their own categories, but you should have a section covering any other legal, regulatory, or corporate requirements. The plan for auditing these compliances should be listed too.

Often, of course, there are none beyond security and privacy.

Your point is fishy. But if the IAU definition changes to "a body orbiting a star", we can rename them to "paparazzi".

[Edited for clarity.] My issue with the IAU's definition is that the body must "orbit the Sun". I would prefer they said "star" instead, and excluded other stars (so a binary star means neither star is a planet).

You remind me of Episode 2 of the Apothecary Diaries: several Chinese troops were poisoned after eating local food. The food was fine, the wood used for fire and eating utensils was the source. I wonder if something like that ever actually happened?