Perhaps we would have more of a chance if we make a collection of international differences in checkmark designs and propose that set of glyphs as a whole.
It doesn't seem like anybody ever filed the paperwork for it. (A search for "krul" on site:unicode.org doesn't turn up anything.) Unicode symbols don't just magically appear! Somebody has to do a bit of work to make it happen. If you're frustrated by a missing symbol, that somebody is probably you!
I am quite sure it has been submitted and rejected before although indeed in my short search just now I couldn't find evidence for this statement.
Edit: Seems like the earlier attempt stopped before ever getting to the proposal stage, maybe it is worth pushing through even though some of the requirements for the unicode standards can not be met.
When you bring up the lower mass and let it go, it seems to push the upper mass away, which should never happen. This whole site smells off vibe coded jank.
A vibe-coded double pendulum sim should produce a much better result than the physics on this page. Claude Code made this just now off one prompt, the physics are much better: https://keir.is/swinging
In theory a get request sent to a server should not have any side effects and only retrieve some data. In practice implemention is completely up to the developer and their rule is about as useful as putting up an exit sign to prevent people from entering your building.
I think even for a company like TSMC these ideas are important to understand.
To give you an example TSMC might have a factory with 10 expensive EUV lithography tools, each capable of processing 100 wafers per hour.
Then they have 4 ovens, each able to bake batches of 500 wafers per hour.
TSMC could improve efficiency by reducing the number of ovens, because they are running only at 50% capacity. But compared to the cost of the EUV tools, the ovens are very cheap. They need to be able to produce at full capacity, even when some ovens breakdown, because stopping the EUV tools because you don't have enough ovens would be much more expensive then operating with spare capacity.
You can do something similar, no? std::pow is not constexpr (most float stuff is not, presumably due to floating point state) but you can implement 10^x anyway
reply