4 ms·
Specs are not meant to be read by average developer. Average developer should read books. Specs are meant to clarify moot points between different implementatio
by vbezhenar 9y ago
Specs are not meant to be read by average developer. Average developer should read books. Specs are meant to clarify moot points between different implementations. Spec is like legal document, they are hard to read, but they serve their purpose.
- nazri1 9y agoThe thing is it shouldn't be that way in the first place isn't it? Take the golang spec, for example.
- acdha 9y agoI think that’s a very narrow view and it’s far from universally true. While a lot of W3C specs are impenetrable there are many counter examples at the IETF which might not be introductory level but are certainly easier for a developer familiar with the topic to follow. I think this is actually fairly important for two reasons. The first is simply that unreadable specs are just as bug prone as unreadable code, but the second is that this increases the distance between the web as specced and the [much much much] larger developer community, and things like <img srcset> / <picture> show the benefit of having less of a communications chasm between those groups. That doesn’t mean that specs can’t be precise but simply that good technical writing can accommodate a wide audience.
- ygra 9y agoI think it also largely depends on what the spec describes. XML for example is rather abstract and can be hard to follow, but SVG is quite easy to read and in my opinion much better than any 3rd-party explanation (primarily because it's complete and error-free).
- dmix 9y agoThese specs are still designing systems that will be used by humans. If they can't be communicated effectively by the designers then it's likely they are too complicated themselves. It would be a good exercise to require the public documentation parsable by humans. At least when it gets beyond the proposal stage.