![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Sep. 8th, 2010 06:28 amImagine you're a tech writer, writing a protocol specification... No, imagine you're a working group designing a network protocol, striving to put as much data as possible into some 140 octets, taking care of predictable and easy decoding and backward compatibility etc.. There are really important things to decide, too, like this one:
If there be a discussion...
``Who would use that stupid #x01? From my experience, GTFO is to be put in its place!''
``You guys, like, have never been a teena^H^H^H^Hypical SMs user. Where is `depressed'? Who needs this `sceptic' at #x02?''
``Calm down, do we have to illustrate #x0C here?''
``Are we having revenge of the nerds or what? Look what I propose for #x0D''
But apparently there wasn't: debates over code space allocation are impossible when 240 of 255 code points is free.
A phrase to start a sci-fi novel (probably about robots' romantic relationships): ``Of course she loved him too, but in a very manufacturer-specific way.''
If there be a discussion...
``Who would use that stupid #x01? From my experience, GTFO is to be put in its place!''
``You guys, like, have never been a teena^H^H^H^Hypical SMs user. Where is `depressed'? Who needs this `sceptic' at #x02?''
``Calm down, do we have to illustrate #x0C here?''
``Are we having revenge of the nerds or what? Look what I propose for #x0D''
But apparently there wasn't: debates over code space allocation are impossible when 240 of 255 code points is free.
A phrase to start a sci-fi novel (probably about robots' romantic relationships): ``Of course she loved him too, but in a very manufacturer-specific way.''
