uranusjr

In the OG RFC 2396, each _path segment_ can specify parameters similar to query parameters, but using a semicolon to separate them to the main segment value instead of question mark. This has effects e.g. when calculating relative URLs. This is now obsolete, but many URL-parsing libraries have an API for that for compatibility.

This happened just last year IIRC in Korea. Nothing was in serious danger (except maybe some travel schedules). A comment already described the mechanism and why that’s not really a thing to worry about.

Because merging into main better exposes the proposal to a more diverse crowd and attracts needed feedback. Especially when you’re managing multiple proposed features, it’s not viable for a mass of users to check out and test those from their individual branches. Without merging fast, you can only gather opinions from people actively reviewing patches, which are a far more minority group and likely to be biased.

Forwarding itself is trivial, just ~5 lines in __getattr__. The difficulty comes when you need to type check the thing. Fixing that would require some special treatment on the type system side and not really doable with a third party library.

They offer educational content. From limited consumption I would not rate it as high quality. More like acceptable I guess.

> The few people who do need it every day can probably work it out for themselves.

People are much less sensitive to their own body odor than you may assume. Please default to taking a shower before you go to public places unless you have very concrete evidence otherwise.

I don’t know the exact history, but the rest of the metric system is designed with a base unit and decimal derivatives. Assuming we want to keep the day length consistent (I can’t imagine a system being practically useful otherwise), we’d have decidays, centidays, etc. and not have hours, minutes, and seconds in the system at all. A system with days, decidays (2.4 hours), millidays (1.44 minutes), and microdays (0.0864 seconds) doesn’t seem bad to me at all, I’m sure people would come up with a good name for 10 microdays for daily use (0.864 seconds).

I think the parent’s logic is the other way around: the rule of law isn’t overwhelmingly relevant in China, so it’s no surprise the VPN law isn’t enforced. You may want to contend if China has the rule of law, but that’s the premise in the parent message, not the conclusion, so you need to use something else to raise objections toward it.

I’m pretty sure they started put as the exact numbers and were just shortened eventually for convenience. This kind of compound word shortening happens all the time in all languages, it’s just Korean happens to have it for numbers, not particularly related to the numeric system as suggested.

I have this done to me a lot and honestly don’t feel a thing. People don’t really care about other people’s coding styles anyway (except they all suck); the thing got done, everyone got credit. I guess everyone feels differently.

Side note, but do you mean it reeks of a witch hunt? (Just making sure.)

I’m really unsure about the Chinese milk scandal analogy. While the Vioxx incident is definitely terrible on its own and may indicate the US government and merchants do not take enough responsibility, the comparison to the melamine is awkward at best; one is a new drug with possible negative health implications (for whatever reason), while the other is a food product with an already illegal additive. It’s not particularly useful to compare the reactions toward the two.

I believe it’s more like half of the Japanese gairaigo (Chinese excluded) come from English, not half of the entirety of Japanese.

Welcome to the Python community, where type highlighting is a first class syntax feature, but actually checking it is optional (unlike the TypeScript compiler), and you get people complaining their favourite languages is polluted by ugly stuff they don’t ever use (presumably) hurting readability. You can’t please everybody.