3 ms·
> To make the API less tedious to use, short protocol name, e.g. "ws", SHOULD be preferred to the long name, e.g. "websockets". Well that's a classic dumb mist
by jheriko 10y ago
> To make the API less tedious to use, short protocol name, e.g. "ws", SHOULD be preferred to the long name, e.g. "websockets".
Well that's a classic dumb mistake.
Programming isn't about typing.
Why not save everyone the effort of having to learn pointless things or look things up? There is no ambiguity with "websockets" where as "ws" describes nothing without context.
- rumcajz 10y agoAnother example: use "tcp_connect" instead of "transmission_control_protocol_connect".
- jheriko 10y agoi'd make an exception for that, but it has nothing to do with the length of the function name. TCP is much more well known as an abbreviation than long hand (most people who use it do not actually know what it stands for) communication is about getting the intent across and not obscuring it after all...
- rumcajz 10y agoYet one example: "dccp_send" or "datagram_congestion_control_protocol_send" ?