Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw
 
PerlMonks  

Re: Larry vs. Joel vs. Ovid

by andye (Curate)
on Nov 21, 2001 at 16:17 UTC ( #126761=note: print w/ replies, xml ) Need Help??


in reply to Larry vs. Joel vs. Ovid

++Ovid, interesting post.

I have to pick you up, though, when you say that W3C standards are, in effect, a variant of Design by Contract. You know what you have to send and, in return, you know exactly what to expect. I don't think that this is true.

Going back to the first HTML rfc (#1866) (and this is historic-interest-only) we see the usual RFC-style vocabulary:

Here's part of the glossary:

should If a document or user agent conflicts with this statement, undesirable results may occur in practice even though it conforms to this specification.
So a browser could adhere to the spec without supporting every part of that spec. It's the same in most of the RFCs - there's shedloads of HTTP that hardly any applications support (e.g. PUT).

To me this seems fairly widely divorced from the idea of 'Design by Contract'. Far from knowing what to send, and knowing what to expect back, it's more like knowing what you could send and what you might receive.

The existing (stricter) standards have evolved from this permissive base - I wonder how much this permissiveness drove their widespread adoption?

andy.


Comment on Re: Larry vs. Joel vs. Ovid
Download Code

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://126761]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others chilling in the Monastery: (10)
As of 2014-12-26 07:18 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    Is guessing a good strategy for surviving in the IT business?





    Results (167 votes), past polls