3 ms·
Programming has grown enormously as a discipline since the 90s (not to mention the tools of the web themselves) and the specs are kind of a pain to read. I read
by jolux 6y ago
Programming has grown enormously as a discipline since the 90s (not to mention the tools of the web themselves) and the specs are kind of a pain to read. I read them when I want an answer to an extremely specific question (what does the spec say about internal implementations of JavaScript objects?) but when I want things like API overviews it’s just faster to have high-quality secondary sources.
- cesaref 6y agoBack in the 90s it was assumed that specs would be written in a specification language, and we'd be able to prove our software by automated testing using the pre/post conditions. We'd mainly spend our time writing UML and thinking back to the bad old days when writing software was using old fashioned text editors like vim and emacs, and we'd be wondering how those fools managed to get anything done. Meanwhile back in reality, it's the same old.
- jolux 6y agoHaha. I was only born in ‘98 so I guess I’ll never know the feeling. Proud Emacs user myself.