Kogasa

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

It depends on what you mean by well defined. At a fundamental level, we need to agree on basic definitions in order to communicate. Principia Mathematica aimed to set a formal logical foundation for all of mathematics, so it needed to be as rigid and unambiguous as possible. The proof that 1+1=2 is just slightly more verbose when using their language.

It’s not a 360 page proof, it just appears that many pages into the book. That’s the whole proof.

It can be, usually for college credit though

At the universities I went to, Calc 2 was integration, sequences and series, then Calc 3 was multivariable. They really pack all the harder parts into 2.

It’s a reach, but the Fourier transformation of a Schwarz (rapidly decaying) function is also a Schwarz function. Compact support is a strictly stronger condition than Schwarz (the function must eventually decay to 0) but doesn’t have this nice property with respect to Fourier transforms, i.e. the FT of a compactly supported function is Schwarz but not necessarily compactly supported

I’m stuck on the homological algebra exercise

You’d still need to manually install the git hooks though, the .git folder isn’t part of the repo

Pre-commit hooks aren’t committed to the repo though. What’s to disable? Unless it’s something like python’s precommit module I guess

You look like you could turn runes into strength

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

Don’t think it saves bandwidth unless it’s a DNS level block, which IT should also do but separately from uBO

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.

You can’t disagree with the fact that Nullable<T> works a lot like an Option<T>. Returning an error is not idiomatic C# code (which would be to throw an exception usually) but if you wanted that, you’d use a Result<T, TError> type or similar.

It’s okay, I don’t take it personally. It’s just such an odd thing.