213 karma · joined July 19, 2015
https://www.ietf.org/rfc/rfc4627.txt says "The names within an object SHOULD be unique". https://tools.ietf.org/html/rfc7159 is more lax and instead says "An object whose names are all unique is interoperable in the sense that all software implementations receiving that object will agree on the name-value mappings". It's unfortunate that the correct behavior is not agreed on and today we saw the consequences of that.
> Sometimes logs can be useful, but only after your monitoring system has told you which system is not behaving, and then you can turn on logs for that system until you've solved the problem, but you shouldn't need access to old logs, because if the problem was only in the past, then it's not really a problem anymore, right?
Some things happen rarely, but can still have large impact. E.g. Imagine a once a day job of moving files which fails twice a month, rendering those files inaccessible.
That really confused the whole discussion as the current situation is tax on land + improved value, making it look like you were arguing from the other side. No tax at all is anyway taking it to the extreme as the government need money, so it becomes merely an academic exercise.
[1]: https://github.com/styled-components/styled-components/issue...
[1] http://www.myfamilydentist.ca/glycerin-and-remineralization-...