Kogasa

Your first sentence asserts the claim to be proved. Actually it asserts something much stronger which is also false, as e.g. 0.101001000100001… is a non-repeating decimal which doesn’t include “2”. While pi is known to be irrational and transcendental, there is no known proof that it is normal or even disjunctive, and generally such proofs are hard to come by except for pathological numbers constructed specifically to be normal/disjunctive or not.

foo terminal foot

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.

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

No, I stand by it. People who cry about straight representation are goblins at best. That’s who’s being mocked, not straight people.

Disrespecting fragile cretins who need to pandered to at all times

Fractal makes a few good cases, OP’s being one of them. The Define series is more about low volume + high capacity than airflow. All of their cases should have GPU clearance specs so you can tell if you have enough space before buying

Paru was at one point a rewrite of yay in Rust, and has since continued development as a pseudo parallel fork. It’s good. Dunno if it’s worth switching, you’d have to see if there’s any specific features you might happen to want, but they’re both fine

Yeah. Normal whoppers are crunchy. 1 in 4 whoppers is soggy and chewy and hard to eat

Whoppers are good but the risk of getting a bad one is not worth it. Ech

I got that banana for my cat. I think the catnip wears off or something but he still likes to have it near him.

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

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?