FedEx Tracking XML Schema
-
@Gąska said in FedEx Tracking XML Schema:
@Jaloopa actually it's Tom's Obvious, Minimal Language. It should come as no surprise that the creator's first name is Tom.
That's even worse
-
@Groaner said in FedEx Tracking XML Schema:
bloated file format compressed surprisingly well in my testing. To anyone familiar with how compression algorithms work, this should be non-intuitive,
I'm no expert on compression, but from what I know, I'd expect a bloated format to compress rather well, at least if the bloat is made up of a lot of repetition — white space for indenting hierarchy, same tags used repeatedly.
-
@Gąska my home network is still ipv4 only, the isp is "rolling out" ipv6 only since 2009...
-
@pie_flavor
Why are we comparing TOML with JSON again? The intended use cases are completely different: One is meant to be a configuration file format and optimized for that, while the other is meant to be used for serialization.Of course, you can abuse TOML for serialization and JSON for configuration files, but why would you do that? (Yes, I'm aware that JSON is often used for configuration files, but just like XML, it sucks at that.)
-
@dfdub said in FedEx Tracking XML Schema:
@pie_flavor
Why are we comparing TOML with JSON again? The intended use cases are completely different: One is meant to be a configuration file format and optimized for that, while the other is meant to be used for serialization.Because @pie_flavor is using TOML for serialization. I know, it's retarded.
-
@dfdub I don't really consider using JSON for configuration as being too bad. It can do a key-value pair list without too much nonsense around it. It's not great, sure, but it's not stupid.
(We use Java so it's .properties files which do that job better, and .ini is good too. But I'm not going to try to kill someone who uses JSON for it.)
-
@bobjanova said in FedEx Tracking XML Schema:
I don't really consider using JSON for configuration as being too bad.
A configuration file format that doesn't support comments is crazy.
And even if you use a non-compliant JSON parser that accepts comments, there's still a lot of syntactic overhead for a user-editable file. To make things worse, it's easy to make typos that result in unrecoverable errors.
-
@Mason_Wheeler said in FedEx Tracking XML Schema:
It's human-readable in the same sense that source code is
Not really. There are plenty of JSON generators that will spit the stuff out without more than the absolute minimum whitespace and with no newlines. A lot of tools choke on lines longer than a megabyte…
-
@dfdub said in FedEx Tracking XML Schema:
And even if you use a non-compliant JSON parser that accepts comments
{ "# comment.1": "you do know that you can hack it?", "# comment.2": "it's only _slightly_ ghastly...", "foo": 0, "bar": 1, "grill": 2 }
(Item names starting with
@
tend to relate to schemas.)
-
I use
.yaml
for config files.Wait, developer confessions is .
-
@error said in FedEx Tracking XML Schema:
I use .yaml for config files.
I guess that explains all the accidental @fbmac_bottings with your new errorbot modules
-
@error said in FedEx Tracking XML Schema:
I use
.yaml
for config files.Wait, developer confessions is .
From my limited use of YAML I haven't run into any of the strange problems with it that I've heard about, but I'm told they do exist
-
@hungrier The weirdness starts to really rear its head once you start to do things with cross-references.
-
@hungrier said in FedEx Tracking XML Schema:
From my limited use of YAML I haven't run into any of the strange problems with it that I've heard about, but I'm told they do exist
YAML is like a lot of other complex languages: If you use the good parts of it, it's fantastic. Just stay away from its crazy parts and you'll like it.
-
@hungrier The parts of YAML you actually use are okay. But the spec contains a million things you'd never use.
-
@pie_flavor Sounds about right. I've used it for Docker Compose and Java configuration, and in both cases it's basically just a .properties file with reduced repetition