spec

That discussion led to a change in the spec [3].

Because I posted the spec list of the tablet.

It works, but when working outside of the spec you should be aware of it a accept shortcomings.

Not picking on Seagate here, they are all similar, but lets look at their Barracuda drive's spec sheet [1].

If and when they drop behind again, they'll be back to talking about more qualitative aspects.

They also have plugins for phylogenetic trees, plots, species names, gene names and reagents.

It's ok if the specs aren't so fancy... a detailed map of what goes on the screen and what everything does is probably fine.

Doing specs in small quick chunks, then writing code, is probably the best approach for lean/agile startup teams that don't yet have customer/product fit.

Noise is particularly useful on large areas, especially those with gradients.

No, it looks to me mass-manufactured to spec by someone or something who doesn't have a say in its design or the ability to individualize it.

All without inventing any half baked new language, file format, virtual machines or whatever else, and building on a language spec that's already an ISO standard.

SMB has an extension mechanism and SMB 1 has support for Unix extensions for over 15 years - I was the author of the original Unix extensions spec.

Now, we have a much more well-specified English language spec that explicitly addresses the challenges of the grammar, with a test suite that does a much better job of covering the corner cases, and much better default implementations.

Wow, I wasn't expecting my email to Jeff to end up as a front-page blog post!The point here is that Markdown doesn't have a spec, nor do any of its variants to my knowledge, so I was proposing to come up with some Markdown-like language that does have a spec.