Clay McLeod

> Regarding the thoughts on the performance impact of the current design, I'm afraid I'm going to have to ask for a bit of clarification by what you mean by...

> I have considered (re)adding lazy records, which would parse fields upon first use. It would help read-only applications that only use a subset of fields, but it would not...

I just tried Michael's latest changes (at https://github.com/zaeleus/noodles/commit/b6f24b78a0ef4e1299908f6cd82edbed3c4dbe26), and the results appear to be huge in terms of speed up. For instance, I'm rewriting part of our [`ngsderive`](https://github.com/stjudecloud/ngsderive) application in...

Hey Mike, Just wanted to say that for our team, this would be really interesting. It's really just a matter of technology selection and not for any real technical reason....

@mlin any updates on the priority of getting this into miniwdl? Just checking in.

I wonder if Markdown may be a better choice for this material: at this point, Markdown is relatively ubiquitous and can be easily translated into a variety of mediums (including...

> The maintainers of these documents are familiar with Markdown. Yeah, sorry, the point here was not say "here's this new technology, _markdown_" (😄). I actually have recently switched to...

> Being able to target multiple output formats to provide easier to process versions for screen-readers and language translation engines is obviously helpful. That doesn't mean markdown should be the...

@ohofmann out of curiosity, is your issue with the header the same as @sc13-bioinf‘s (the lowercase platform name)? Internally, we have been brainstorming some computationally feasible ways to provide an...

I have also thought about this quite a bit from the other perspective—I think that, philosophically, perhaps the spec and users think of rigidity in the header differently. One *could*...