Conversation

it grew out of the observation that people keep inventing self-describing data formats and there isn't any real forward progress, instead the same few ideas get cycled through on a period of 10-15 years.
1
4
we decided that self-describing data is the wrong problem. or at least, it's a thing people need but not by itself a hard thing to make. the reason we're never satisfied with the ones we have is *schemas*.
1
so we came up with a schema format for dependently-typed object graphs. it's a compact binary format, mostly to help people resist the temptation to edit it directly as text and then be upset that its text representation doesn't meet their standards of beauty.
2
6
notionally this could subsume any existing data format, whether self-describing or not. and then you could have a whole tool stack built on top of it - equivalents of diff, version control, grep, structure editors... but the tools would work on any data you had a schema for.
1
3
anyway it's a lot of work and, while it would benefit the world, we think we can do more to help the world in the political domain rather than by spending our time building things.
1
1
Oh neat! I'm currently making a dependently typed data description language at - the intension is to describe existing binary data formats, but that is a big challenge, hehe. Trying to chip away at it. I really like the sound of this!
1
5
yeah the challenge is basically that most of the people who understand dependent type checkers are mathematicians rather than programmers. so all the explanations of it are, um, abstract.
3
4
Show replies