China does have some car brands that support battery swapping, with NIO being a notable example that markets this feature. However, their market share isn’t particularly high. It can be said that battery swapping is a common practice in China, but it isn’t the primary method for electric vehicle energy replenishment. Incidentally, NIO vehicles don’t support particularly high charging speeds. High-speed charging can impact battery lifespan, so manufacturers like NIO also prefer to avoid promoting fast charging from their perspective.
> `Object` is translated to `宾语` which means the grammar component object in subject, verb, object, etc.
Sounds right (though OOP treats objects artificially as grammatical subjects, they are the things on which functions operate, and thus more like what would normally be grammatical objects; they are the patients rather than the agents of actions.)
Ouch. Sounds like they’re using a general-purpose, not domain-specific, dictionary for their translations. That might suffice for an initial private proof-of-concept, but not for a public audience.
Imagine translating a medical or legal textbook without knowing the proper professional medical/legal terminology. Those target audiences will tear it a new one, and quite right too.
The word "object" in object-oriented programming is best translated as "thing" or "entity". It has nothing to do with grammar; it's representative of "things" with properties and capabilities. If you want to get grammatical, what of ergativity?
> It seemed difficult (impossible?) to pay with anything but cash
That's true and it is not convenient for visitors. Local people usually just use public transportation card (magnetic/contact-less smart card) everyday and don't have to pay with cash (you can charge the card with credit card or Alipay). Some station gates also support paying with NFC smartphones (eg. Xiaomi), and I think that's modern :-)
It's not too hard, with a bit of diligence (and a phrasebook), to get a contactless card as a foreigner. Although it is still easiest to add value with cash through one of the station attendant booths.
Security headers are worthy of a different [1], lengthy conversation, but they were borne out of need to override defaults about a browser's security features.
Sometimes, for different features, those defaults are permissive, and sometimes they're restrictive, provided the browser supports that header -- and most of them were designed to be backward-compatible so that their truth tables are complicated.
But realistically, consider C-S-P as metadata about the resource representation about to be delivered in the body, instead of a property of the HTTP response itself. In fact, the naming of the header 'Content-[...]' is consistent with the semantics of RFC 7231 [2] which defines a number of different 'Content-[...]' headers, like 'Content-Type' and 'Content-Language'. You can mentally move C-S-P from the HTTP headers into a meta tag (you can do this actually [3]).
You get 192 -> 100 bytes reduction if there's only one response. The compression dictionary(dynamic table) is shared, therefore much more bytes can be saved in the following responses(assuming they contain similar headers).
