mojombo

10 ms·

61.
by mojombo 8y ago
This is covered quite extensively in the podcast, but the quick version is that we went to a PHP conference very early on to exhibit and found something like half the people that stopped by our booth thought GitHub sounded cool and would be
62.
by mojombo 8y ago
Tom here. Just saw this got posted on HN and wanted to say I’m happy to answer any questions about how we tackled Enterprise at GitHub (the main topic of the podcast) or anything else, really!
63.
by mojombo 8y ago
Not currently, but it's something I'd like to add as a separate spec sometime later.
64.
by mojombo 8y ago
Yeah, they're ok for very simple use cases, it's when you start having more than one level of nesting that things get a little crazy.
65.
by mojombo 8y ago
Yeah, I'll agree with that, among many other issues with YAML. =) A schema would at least solve that problem, but I don't think most simple config users want to define a schema, so strong typing is a better solution.
66.
by mojombo 8y ago
Protocol Buffers is a data serialization format and unsuitable for configuration, as the binary serialized data is not human readable.
67.
by mojombo 8y ago
Dave and I worked together at Powerset many years ago (pre-GitHub) and wrote a bunch of Erlang together. We have a lot of inside jokes from those days. LEAVE HIM ALOOOOOOOOOOOONE!
68.
by mojombo 8y ago
Hah, sorry! You can always release an 0.4 compatible first, and then add the stuff from 0.5. Sounds like a great project!
69.
by mojombo 8y ago
You're welcome, really glad you like it, and good to know the double square brackets make sense to you! It does seem to be a bit polarizing, so we'll keep working on something even better.
70.
by mojombo 8y ago
I have not, and while it looks cool, it seems to be optimized for data transfer between applications, not a human readable config format.
71.
by mojombo 8y ago
Oh, you mean you want something like: list = [ "1.0", "2.7", { version = "1.4", path = "..." }, "9.9", ] Is that correct?
72.
by mojombo 8y ago
Yeah, Cargo and Rust have been really important in TOML gaining adoption. Love the Rust community!
73.
by mojombo 8y ago
I'm always in favor of small config files, but sometimes for larger projects that's just not possible (or desirable). TOML has always been about being as simple as possible while still solving a wide range of problems. But I think
74.
by mojombo 8y ago
Awesome, sounds like the perfect use case for TOML!
75.
by mojombo 8y ago
It's never useless to say thanks! I really appreciate your kind words, it's the fuel that powers a lot of open source. Keep it up!
76.
by mojombo 8y ago
Curious. In order to be part of one of the tables in the [[something]] array, a table would need to be named [something.X]. What parser are you using? it's possible that it's behaving improperly in this case. See the relevant part
77.
by mojombo 8y ago
The limitations are mainly around nested arrays of tables. As has been mentioned here already, the [[array-of-tables]] syntax that currently allows this can be super confusing, and is definitely the worst part of TOML right now. Even so, yo
78.
by mojombo 8y ago
Amazing, thanks for the heads up! I'll add it to the list of projects using TOML [1] and take a look at your example configs to get some more real-world uses cases to look at when evaluating future changes to the spec. [1] https:&#x2F
79.
by mojombo 8y ago
As it should! It was inspired by INI, but with a desire for a proper spec that unambiguously maps the config file to a hash table.
80.
by mojombo 8y ago
Absolutely. That's what I mean about TOML mapping unambiguously to a hash table. Strings in TOML are always quoted. There is no fuzzy interpretation of things like YES and NO. That way madness lies. I also am not a fan of meaningful wh
81.
by mojombo 8y ago
Homogenous arrays are partly to make implementations easier, and because if you really need that flexibility, you can always use an array of inline tables, which has the benefit of giving each sub-element a name, hopefully increasing the ob
82.
by mojombo 8y ago
Hi Dave! Ponies come standard in TOML, you just have to know where to look. =)
83.
by mojombo 8y ago
Glad you like them, we spent quite a bit of time getting them right! Datetimes are a horrible mess of complexity, but hopefully over time languages and tools around them can standardize on a set of common primitives to make all our lives a
84.
by mojombo 8y ago
Yeah, TOML is definitely INI inspired, but there is no canonical INI spec. I wouldn't say that TOML is INI, though. INI files still exist in their variously poorly specified ways.
85.
by mojombo 8y ago
1. How would the file path type differ from a regular string? Would you want specific semantic validation for each platform? 2. This is still a big question, and we've been having a robust argument about it on GitHub [1]. It's a p
86.
by mojombo 8y ago
Well, it was only a joke to begin with. I couldn't stand the complexity or ambiguity of YAML and one night I had a few drinks and banged out my thoughts on something better. When people started writing implementations, I realized that
87.
by mojombo 8y ago
Yeah, it's not my favorite part either. We've made them mostly unnecessary by adding inline tables, but for heavy nesting of arrays of tables, you still need to use them, which is why I mentioned that there are still some weakness
88.
by mojombo 8y ago
Yes, we just released it two days ago! I know v1.0.0 has been a long time coming, but it's important to me that we get it right, as specs have a very long-lasting impact (much more so than a specific version of a library). We are indee
89.
by mojombo 8y ago
We added a proper datetime type because the only thing worse than having one is not having one. If you had to supply a datetime as a string, every TOML file would have a different way of doing it, which is...not so obvious.
90.
by mojombo 8y ago
Hey, Tom here (creator of TOML). Fun to see TOML on HN again! Since I first wrote a (mostly) joke proposal for TOML 5 years ago, TOML has been adopted by a number of prominent projects such as Cargo, Hugo, Pipenv, and others. TOML is especi

More ›