36 ms·
I never understood the idea of shortening variable names a few characters. Recv vs Received, especially when there’s a also a Rec type mentioned in the reader a
by syspec 8y ago
I never understood the idea of shortening variable names a few characters. Recv vs Received, especially when there’s a also a Rec type mentioned in the reader as well.
It’s not like Send, was shortened to Snd
- hu3 8y agoQuite confusing indeed: Rec<Recv<String, Var<Z>>>
- userbinator 8y agoRead (or indeed, write) a lot of code and you'll quickly realise why. It's the same reason acronyms and abbreviations exist in human languages. Also, "recv" and "send" are both 4 characters, which is nice.
- nitrogen 8y agoThese days people type the first four letters and rely on IDE autocomplete to finish the other 42.
- oh_sigh 8y agoProbably because someone important couldn't remember if it was receive or recieve
- theoh 8y agoIt's mysterious, all right. https://unix.stackexchange.com/questions/128708/why-wasnt-creat-called-create https://unix.stackexchange.com/questions/128708/why-wasnt-cr... The case where things are given three or four letter codes is more comprehensible. Baudot code from the 19th C calls letters and figures LTRS and FIGS, though I'm not sure when exactly that got established as the normative spelling. Presumably LTRS and FIGS can be printed on a smaller keycap than the full word. https://en.wikipedia.org/wiki/Baudot_code https://en.wikipedia.org/wiki/Baudot_code So at a certain point abbreviations became both useful and fashionable: https://en.wikipedia.org/wiki/Abbreviation https://en.wikipedia.org/wiki/Abbreviation (See also http://www.thepotteries.org/mark/w/wedgwood-date.html http://www.thepotteries.org/mark/w/wedgwood-date.html for a 19th C example of three-letter coding.)