FWIW the second part does not address my concern (which was about omitting literal parentheses that are present in the markup, in some cases), though it is related. Personally I think it's already a mistake for bare/unescaped words to indicate markup, or I guess the intention is that they indicate mathematical semantics and then Typst decides the best way to write down that semantics unless you explicitly interfere -- seems like a recipe for confusion whenever Typst's ideas of the mapping from semantics to typography don't quite line up with yours, or the conventions in your field. I'd much rather approach mathematical typesetting with a typesetting language than a mathematical language where somebody else has decided how that math should be typeset, even if it means a sea of backslashes and curly braces.
(Edit to add: I guess this means my preference would be option E from the blog post -- I see the extra symbols as far preferable to the ambiguity between content and markup)
Also wow, recovering from this breaking change is going to be incredibly painful for somebody.
I think social biases (e.g. angry black women stereotype) in your paper is different from cognitive biases about facts (e.g. number of legs, whether lines are parallel) that OP is about.
As far as the model's concerned, there's not much difference. Social biases will tend to show up objectively in the training data because the training data is influenced by those biases (the same thing happens with humans, which how these biases can proliferate and persist).
> a bit like trying to explain a vacuum cleaner to someone who has never seen one, except you're only allowed to use words that are four letters long or shorter.
> What can you say?
> "It is a tool that does suck up dust to make what you walk on in a home tidy."
I liked that the original explained the value of the vacuum cleaner. It's not that it removes dirt and dust per se, it's that it makes spaces you walk on tidier.
Oh come on, this shit is easy. Why did they say "it is" and not "it's", by the way? To put it that way can't help. So yeah, it's a pipe that can suck, and you push it all over your room, to suck the dust and dirt up off the rugs and such, and in fact off of any low down flat part. One kind can even move on its own! But what I want to say here, in the main, is that you math guys have all lost your grip on how to say any idea in an easy form. You are not able to do it any more, 'cos too much math has made you sick in the head.
I feel like there's still room to avoid pidgin while making it less awkward, e.g.: "It's a tool that can suck up dust or dirt to make your home more tidy."
> Cost of goods sold (COGS) refers to the direct costs of producing the goods sold by a company. This amount includes the cost of the materials and labor directly used to create the good. It excludes indirect expenses, such as distribution costs and sales force costs.
So the $550 or $650 COGS includes the cost of labor for manufacturing, but excludes (say) marketing and auditing costs.
Right, but this is the same company, so the cost of marketing, auditing, R&D, etc. shouldn't be different for these products. That's a fixed cost for the company.
This is a guess, but the argument is probably that it took way more R&D effort for them to figure out how to produce it efficiently in the US, and they've chosen to increase the cost of the US phone variant to offset this particular R&D expenditure that the Chinese variant didn't have.
> So it's about $650 to produce that entire phone. But what we're doing by selling it for greater originally, we're looking at a lot of differentiators for us. It wasn't just made in the USA. It's the fact that it's a secure supply chain, that you know, staff that's completely auditing every component, which means we're selling to a government security market with all those additional layers that we've added on top.
So I guess the answer is that they're selling to the "government security market" so they can charge whatever the hell they want.
> Chinese newspaper Economic Observer earlier reported that local traffic police had told the father of one of the victims that the car had caught fire after hitting the cement pole, and the car key had not unlocked the door.
> When the app is opened for the first time, it waits a few seconds to call the geolocation API. This way, the App Store’s automated review process doesn’t see anything unusual in the app’s code. We also checked the app’s behavior by running it through a proxy to fake our location to San Jose, California. For this location, the app never reveals its hidden interface.
> After Apple approves the app with its basic functionalities, developers use CodePush to update it with anything they want. The app then reveals its true interface in “safe” locations.
Apple have locations all over the world they can test from and a proxy-like service they sell to users called “Private Relay”. They have all the necessary tools to easily combat this, except the staff to do so.
BTW, I notice that both of your complaints will be addressed in the next version:
https://github.com/typst/typst/pull/6672
https://github.com/typst/typst/pull/6442 , see also https://laurmaedje.github.io/posts/math-mode-problem/