lime
they are also working on a follow-up, uv. not really a fan of writing tooling in another language but it works really well.
honestly i expected the fifth panel to be full of things like "GIL", "2to3", "virtualenv" "pip vs conda vs poetry vs...", "mypy", etc
i don't think any manufacturer publishes the voltage their devices run at, could be anywhere from 3.3 to 5V. so i don't know how an end-user is supposed to compare battery sizes between devices.
you would be a bit peeved as well if one guy in a lecture hall with 150 people constantly asked you to convert every measurement in your talk to something only that guy understands.
the spec is 10 chapters. everything is unquoted by default, so parsers must be able to guess the data type of every value, and will silently convert them if they are, but leave them alone otherwise. there are 63 possible combinations of string type. "no" and "on" are both valid booleans. it supports sexagesimal numbers for some reason, using the colon as a separator just like for objects. other things of this nature.
i can see what it points to. you can't claim the statement is unfalsifiable just because you didn't see the issues before removal. like, this is not proof-of-god tier stuff.
it took you as long to find that link as it would have to look up the thing they gave you. this is not kindergarten, nobody owes you you their time. you are expected to be able to find and evaluate the validity of information yourself.
well in my language they're "runners" so i guess i should have thought a bit harder there...
well, til!
kiwi works fine as a topping. i used to live next to a place that had a whole variety of fruit pizzas.