this post was submitted on 11 Jun 2024

212 points (94.5% liked)

Programmer Humor

32443 readers

1031 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.

founded 5 years ago

MODERATORS

cat_programmer@lemmy.ml

AgreeableLandscape@lemmy.ml

212

XᴍʟHᴛᴛᴘRequest (lemmy.ml)

submitted 5 months ago* (last edited 5 months ago) by toastal@lemmy.ml to c/programmerhumor@lemmy.ml

23 comments fedilink hide all child comments

Acronyms/intialism use capital letters to encode information about words. Losing that information is a mistake. SᴍᴀʟʟCᴀᴘCᴀsᴇ is now considered a best practice.

…Or consider snake_case or kebab-case 🤷

top 23 comments

sorted by: hot top controversial new old

[–] faebudo@infosec.pub 110 points 5 months ago (3 children)

ExtensibleMarkupLanguageHypertextTransferProtocolRequest

[–] dohpaz42@lemmy.world 55 points 5 months ago (1 children)

This person Javas…

[–] elvith@discuss.tchncs.de 36 points 5 months ago (1 children)

Wouldn't that imply the existence of a ExtensibleMarkupLanguageHypertextTransferProtocolRequestFactorySingleton?

[–] IHateReddit@lemmy.world 21 points 5 months ago (2 children)

And an AbstractExtensibleMarkupLanguageHypertextTransformerProtocolRequestFactorySingletonBuilder!

[–] PoolloverNathan@programming.dev 10 points 5 months ago (1 children)

Sadly you can't build a singleton. AbstractExtensibleMarkupLanguageHypertextTransformerProtocolRequestFactoryBuilder$Companion?

[–] toastal@lemmy.ml 9 points 5 months ago

80 char line maximum? I read that as minimum. My bad.

[–] abrahambelch@programming.dev 4 points 5 months ago

AbstractExtensibleMarkupLanguageHypertextTransformerProtocolRequestFactorySingletonBuilderDecoratorDelegationStrategyDispatcher

[–] eager_eagle@lemmy.world 26 points 5 months ago (1 children)

Doing that with GNU or WINE will use your entire memory

[–] Feathercrown@lemmy.world 4 points 5 months ago

GNU's Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix Not Unix CORE DUMP: OUT OF MEMORY EXCEPTION

[–] crispy_kilt@feddit.de 2 points 5 months ago

Needs more AbstractSingletonBeanProxyFactoryDefaultImplementation

[–] toastal@lemmy.ml 19 points 5 months ago* (last edited 5 months ago)

Acronyms/intialism use capital letters to encode information about words. Losing that information is a mistake. SᴍᴀʟʟCᴀᴘCᴀsᴇ is now considered a best practice.

…Or I dunno try snake_case or kebab-case 🤷

[–] yogthos@lemmy.ml 9 points 5 months ago* (last edited 5 months ago) (1 children)

kebab case for the win xml-http-request

[–] sik0fewl@lemmy.ca 3 points 5 months ago

XML-HTTP-request?

[–] DmMacniel@feddit.de 8 points 5 months ago (1 children)

XHR boom. Sue me :)

[–] Alexstarfire@lemmy.world 7 points 5 months ago (2 children)

OP is dead now. Are you happy?

[–] lord_ryvan@ttrpg.network 2 points 5 months ago* (last edited 5 months ago)

Yes!

May OP request in peace

[–] DmMacniel@feddit.de 1 points 5 months ago

I regret nothing!

[–] JoYo@lemmy.ml 4 points 5 months ago

id throw away all of these if they aren’t struct definitions, which they aren’t.

[–] jimitsoni18@lemmy.zip 3 points 4 months ago

xhr

[+] Boomkop3@reddthat.com -12 points 5 months ago* (last edited 5 months ago) (1 children)

I don't like to sticking to generalized naming conventions when autofill or intellisense is a thing. Make your names clear in whatever way you think works best, and developers still using vim can set up autocomplete using an extension or something

[–] Kraiden@kbin.run 23 points 5 months ago (1 children)

Dear god please no. This way madness lies. Your idea of "whatever you think works best" is not going to line up with whatever the next person that comes along thinks, and your codebase is about to get all kinds of fucked up.

Thinking code complete is going to save you is naive. Even in languages like C and Java, where it works best, you still need to be able to read and understand the code in context. There's no hope in a language like Ruby with all it's meta programming stuff

[–] Boomkop3@reddthat.com 8 points 5 months ago (1 children)

I'm not suggesting randomness or inconsistency, I'm saying generalizing is overkill. But you're right, "whatever works" might be taken too literal by some

You're absolutely right that depending on your autofill is not a good general approach either. Then again, you shouldn't be guessing at these either

I've worked with changing conventions in different teams. In the end people are not going to come up with some name and whether it's myOldThing or my_old_thing won't matter much. Usually I just follow whatever the team I'm working with prefers

[–] Kraiden@kbin.run 5 points 5 months ago

Yes and no. I agree that camel vs snake or that stupid mNameThing that was popular for a while, doesn't reeeeeaaally matter, although I would argue that convention over the language still has value. As an example, naming a Java variable with a capital letter would be confusing and annoying to any new devs joining the project, even if it's a valid identifier. Also it's handy to be able to look at something in ALL_CAPS and know that it's probably a static final, without having to check it's definition. I guess it's about finding that line between useful conventions and pedantry.