Kogasa

The eigenvalues of a diagonal matrix are the values on the diagonal. Diagonalizable matrices’ eigenvalues can be determined by diagonalizing them and looking at the entries on the diagonal.

But something has to be written on the birth certificate and social security card, and that’s what everything else will expect you to use. I think just due to technical limitations (e.g. of the printer/template for those things) it wouldn’t be allowed, but I dunno about legally

Keycaps are expensive but you can easily spend $500 on a keyboard chassis/plate/pcb alone

If a line-following robot bumps into a 3 year old, it might knock them over. It’s a different situation with high speed 2 ton death machines

Status 200 for errors is common for non-REST HTTP APIs. An application error isn’t an HTTP error, the request and response were both handled successfully.

There may be a need for additional information, there just isn’t any in these responses. Using a basic JSON schema like the Problem Details RFC provides a standard way to add that information if necessary. Error codes are also often too general to have an application specific meaning. For example, is a “400 bad request” response caused by a malformed payload, a syntactically valid but semantically invalid payload, or what? Hence you put some data in the response body.

This should be done with font ligatures, not replacing character combinations with other characters that can’t be typed normally

Once every 50 years or so

If my cooking senses are right, it would be like cooking bacon in a stainless steel pan, which is sticky and burny but not impossible

No, it isn’t

You’re making assumptions about the control flow in a hypothetical piece of code…

What you’re saying is “descriptive method names aren’t a substitute for knowing how the code works.” That’s once again just a basic fact. It’s not “hiding,” it’s “organization.” Organization makes it easier to take a high level view of the code, it doesn’t preclude you from digging in at a lower level.

No, your argument is equally applicable to all methods. The idea that a method hides implementation details is not a real criticism, it’s just a basic fact.

No, not “almost every modern developer thinks inheritance is just bad.” They recognize that “prefer composition over inheritance” has merit. That doesn’t mean inheritance is itself a bad thing, just a situational one. The .NET and Java ecosystems are built out of largely object-oriented designs.

You realize this is just an argument against methods?

Java is a fine choice. Much prefer it over pseudocode.

I have read programs a lot shorter than 500 lines which I don’t have the expertise to write.

Still not enough, or at least pi is not known to have this property. You need the number to be “normal” (or a slightly weaker property) which turns out to be hard to prove about most numbers.

These things are specifically not defined by the protocol. They could be. They’re not, by design.

It doesn’t, it just delegates the responsibility to something else, namely xdg-desktop-portal and/or your compositor. The main issue with global hotkeys is that applications can’t usually set them, e.g. Discord push-to-talk, rather the compositor has to set them and the application needs to communicate with the compositor. This is fundamentally different from how it worked with X11 so naturally adoption is slow.