676

Welsh or C standard library function? (feddit.org)

submitted 1 day ago by gandalf_der_12te@feddit.org to c/programmer_humor@programming.dev

63 comments fedilink hide all child comments

top 50 comments

sorted by: hot top controversial new old

[-] davetortoise@reddthat.com 47 points 15 hours ago* (last edited 15 hours ago)

rhowch

When scooby burns his tail

[-] I_am_10_squirrels@beehaw.org 2 points 7 hours ago

Shaggy, his arms open wide

[-] umbraroze@slrpnk.net 17 points 13 hours ago

Long ago in the Windows 9x era there was also "Is this a Windows DLL file, or a transcript of a digestion noise" and the stuff was like "MSGRBL32.DLL"

[-] tunetardis@piefed.ca 7 points 14 hours ago

I guess strxfrm and the like date back to a period in the 80s when symbol names had to be kept short for the compiler/interpreter's sake. Like while BASIC back in those days technically allowed > 8 chr names, the interpreter only stored the first 8. In other words, the first 8 needed to be unique. As such, people tended to stick with <= 8 chr symbols to avoid interpreter issues. I think C allowed up to 31? But the culture of <= 8 prevailed nevertheless.

Then in the 90s, such restrictions were largely dropped in most languages, and symbol names ballooned in size to take advantage of this new freedom. In C++, you even had reserved words growing to the likes of reinterpret_cast around that time, but APIs just got ridiculous along the lines lengthy_class_name_followed_by_fully_spelled_out_method.

Today, people seem to have come to their senses and settled on more reasonable lengths, though not to 80s extremes. Like going back to C++, we have new reserved words like decltype and constexpr. In the 90s, these would likely have been spelled out in full like constant_expression?

[-] grozzle@lemmy.zip 6 points 10 hours ago* (last edited 10 hours ago)

i still have a vague mistrust of file extensions longer than three characters.

like a glass walkway, i know .jpeg is just as safe as .jpg, but there's a hint of uneasiness.

[-] tunetardis@piefed.ca 2 points 7 hours ago

I also have a vague mistrust of non-alphanumerics in file extensions. Like while .c++ is fine, .cpp feels…safer?

[-] heartSagan5@lemmy.zip 1 points 1 hour ago

Well, yeah. Why would you tempt the shell to get garbled?

[-] x74sys@programming.dev 1 points 7 hours ago

.cc and .hh feels the most serious.

[-] BigDanishGuy@sh.itjust.works 4 points 12 hours ago* (last edited 5 hours ago)

Then in the 90s, such restrictions were largely dropped in most languages, and symbol names ballooned in size to take advantage of this new freedom.

But with great freedom comes great responsibility. I think Microsoft went from digestion noices to indirectly advertising their stake in arthritis medicine. I mean my fingers ache just looking at C# or PowerShell.

What was so wrong about puts or cout? I know it's not the most intricate functions, but going from a 4chr function to "Console.WriteLine()" is a symptom.

And as long as I'm already a riled up old fart, let me tell you about autocompletion. Why does MS have to autocomplete entire commands from ambiguous strings?

And the kids don't get it. They don't even write the code anymore, let alone understand it... I want coffee flavoured coffee, heavy metal and for dark mode to fucking die!

That felt better, I'm sorry for anybody making it this long.

I'm just an old fart

[-] bridgeburner@lemmy.world 6 points 12 hours ago

Dude what's with ur crusade against dark mode lol. It's not like dark mode replaced light mode.

[-] BigDanishGuy@sh.itjust.works 1 points 8 hours ago* (last edited 6 hours ago)

Waddaya mean crusade? Have you accidentally seen one of my other tirades?

Anyway:

I dislike change. I know it's not a good argument, but I don't like change.
I don't have a lot against dark mode, on a phone. But...
Running an IDE or word processor in dark mode screams unprofessional to me. I work in a well lit office environment, during the day. In a bright office I struggle reading in dark mode.
Using dark mode because you "don't want to have your eyes scorched", is the argument of a hobbyist, working in their bedroom.
I like to view my end product on screen. I'm not printing documents in dark mode, and presentations are more easily viewable with a light background.

It's not an argument for or against dark mode, but dark mode seems like that time, back in the 90s, when people insisted on using a blue background for word processing. We're just going in circles on this.

[-] heartSagan5@lemmy.zip 1 points 1 hour ago

I sometimes do emacs over a terminal because ofc, but some of the font colors are hard to see in dark mode.

[-] rustyj@lemmy.world 1 points 5 hours ago

I was having legitimate eye strain issues before using dark mode in more places. I also only have vision in one eye, so that factor is in the mix. Anyhow, for me, dark mode is more of an accessibility tool, not "some hobbyist thing".

[-] tunetardis@piefed.ca 1 points 7 hours ago

Dark mode to me harkens back to the days of terminals and mainframes. Light mode was popularized by the likes of Apple who believed in the wysiwyg philosophy. A document on screen should resemble its counterpart on paper.

But dark does seem to be in vogue once again. Something I did not see coming, much like how vinyl came back—which also tends to be a dark medium now that I think of it, though I can't think of any reason it really needs to be? Hmm…

[-] fum@lemmy.world 2 points 10 hours ago

In some cases it did. I often come across dark theme only websites.

[-] crapwittyname@feddit.uk 26 points 19 hours ago

Cwtch is one of my favourite words. Pronounced like "clutch" without the L. It means hug.
"Give us a cwtch ye daft old sod" ❤️

[-] heartSagan5@lemmy.zip 1 points 1 hour ago

Sounds like the origin of “clutch of eggs.”

[-] gandalf_der_12te@feddit.org 2 points 11 hours ago

oh wow that's nice. i'll see if i can remember it.

[-] MrScottyTay@sh.itjust.works 3 points 14 hours ago

Wild assumption for me to make, but is it perhaps a potential origin for "coochie coo"?

[-] crapwittyname@feddit.uk 1 points 12 hours ago

Ooh that would be nice

[-] Codpiece@feddit.uk 17 points 19 hours ago

Ah yes. A language forced onto unwilling participants by people who still think it should relevant in the modern age. And the other one is a Celtic language.

[-] calcopiritus@lemmy.world 1 points 7 hours ago

Unfortunately, it's the only sane cross-language ABI option there is.

C++ is a close second, which is mostly because C++ uses the C ABI wherever it can.

Even if the language itself is obsolete, it will live on for many more years just because of that.

[-] Artemis_Mystique@lemmy.ml 21 points 18 hours ago

C will be relevant till the heat death of the universe. if humanity ever dooms itself back to the stone age, all it would require is some bloke to invent a rudimentary binary computer and some nerd to write a basic C compiler for it, humanity will doom itself again in less than 50 years.