Personally, I prefer duplicate keys to be eaten by the parser but I can see how it'd be beneficial to prevent them.
GTG3000
Yeah, I remember when I was trying to parse XML into some lua tables and it forever stumped me how to represent something like
<thing important_param=10 other_param="abracadabra"> stuff </thing>
You just have to have different ways to turn different tags into stuff in your program and that's a huge amount of overhead to think about when all I want is a hash map and maybe an array.
It's inconsistent and annoying. Expressive, yes. Gets it's job done, yes. Absolute nightmare of a spec, YES.
The fact that JSON is a subset of YAML should tell you everything about how bloated the spec is. And of course there's the "no" funny things.
Personally, my favourite way to write configs was using lua (because it was already part of the project so why not), but JSON does fine.
Genuinely, why? Personally, I'm happy to eat basically same meals for a few days before they get boring, and you can vary your sandwiches a lot of you so desire.
I used to use FTP for file transfer, nowadays I just start up a HTTPS server on the source machine and grab stuff from there.
Well, it was a spur-of-the-moment sort of thing when I went and looked at their site and it just had a bunch of names with no numbers there under the book art.
Went and checked now and site looks entirely different, and I can clearly see the issue numbers. I don't know, maybe I hallucinated it.
Yeah. I tried getting into comics once and got a multi-gigabyte archive of deadpool stuff.
...couldn't make heads or tails of it.
Actually couldn't get into IDW sonic/transformers for the same reason. WHERE DO I START!?
Yeah, it's pretty difficult to find energy for personal programming stuff when your dayjob is programming stuff.
Gotta get up from the PC for a bit.
Chernobyl isn't safe safe, it's just safe enough for wildlife to survive there, possibly with lowered life span and quality of life.
Also, there's a decent danger of radioactive dust coming off the book if it's handled. It may not be that radioactive, but if it clings to you, or you breathe it in, it will do considerably more damage than if it was all one solid rock that made geiger counters click.
"speak-singing" is a thing some people do to work around language issues, apparently it's an entirely different part of the brain.
Anything an API returns should just look like 1720533944.963659
.
There's no reason to store dates as anything other than UTC. User-side, sure, timezones are useful. Server doesn't have to know.
Man, the variable scoping thing is insidious. It will never not be weird to me that
if
s and loops don't actually create a new scope.And then you try to do a closure and it tells you you didn't import anything yet.