You can imagine tracing a path along a Klein bottle to see that it only has one side. To get more precise than that requires some topological context. If you slice it down the middle it turns into two Möbius strips and an orientation of the Klein bottle would induce an orientation of the strips, which are non-orientable. Alternately it has zero top integer homology, which you can get from looking at a triangulation. The orientable double cover of a Klein bottle is a torus, which is connected (if it were orientable, the double cover would be two disconnected Klein bottles).

Yeah, specifically for something like coreutils I can't see the malicious endgame that is suggested by others here. Is the fear that a proprietary version of cat or pwd or printf takes over the ecosystem and then traps users into a nonfree agreement? Or a proprietary coreutils superset that offers some new tool and does the same thing? Or a proprietary coreutils that generates profit for businesses without attribution to the developers? What would stop anyone from just writing their own proprietary set of tools to do the same thing now, even if uutils didn't exist? Clearly not much, since uutils did exactly that (minus the proprietary bit).

I personally don't see a compelling reason to change to MIT, but I also don't see the problem.

Choking hazard for small children probably.

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

Would not be surprised if it's getting confused about a wallet sponsorship

bullet_idx

Not true at all, lots of wireless mice with durable optional cables.

IMO every datetime should be in utc, and variables for datetimes should either be suffixed "Utc" or have a type indicating their time zone (DateTimeOffset or UtcDateTime etc). Conversion to local time happens at the last possible second (e.g. in the view model or an outbound http request parameter). Of course that doesn't solve the problem of interoperating with other ~~morons~~ programmers who don't follow these rules, but it keeps things a lot neater locally.

Scheduling based on regional time conventions (holidays, weekends, etc) is just not great though.

It's dynamic :)

It's a great book. It's just got some fantastic competition.

This also works in a big flour tortilla. I usually skip the jelly though.

Alright buddy. Here's your "whole carrot dipped in ranch" salad.