XᴍʟHᴛᴛᴘRequest
https://lemmy.ml/post/16761375
=> More informations about this toot | More toots from toastal@lemmy.ml
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 🤷
=> More informations about this toot | More toots from toastal@lemmy.ml
ExtensibleMarkupLanguageHypertextTransferProtocolRequest
=> More informations about this toot | More toots from faebudo@infosec.pub
This person Javas…
=> More informations about this toot | More toots from dohpaz42@lemmy.world
Wouldn’t that imply the existence of a ExtensibleMarkupLanguageHypertextTransferProtocolRequestFactorySingleton?
=> More informations about this toot | More toots from elvith@discuss.tchncs.de
And an AbstractExtensibleMarkupLanguageHypertextTransformerProtocolRequestFactorySingletonBuilder!
=> More informations about this toot | More toots from IHateReddit@lemmy.world
Sadly you can’t build a singleton. AbstractExtensibleMarkupLanguageHypertextTransformerProtocolRequestFactoryBuilder$Companion?
=> More informations about this toot | More toots from PoolloverNathan@programming.dev
80 char line maximum? I read that as minimum. My bad.
=> More informations about this toot | More toots from toastal@lemmy.ml
AbstractExtensibleMarkupLanguageHypertextTransformerProtocolRequestFactorySingletonBuilderDecoratorDelegationStrategyDispatcher
=> More informations about this toot | More toots from abrahambelch@programming.dev
Doing that with GNU or WINE will use your entire memory
=> More informations about this toot | More toots from eager_eagle@lemmy.world
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
=> More informations about this toot | More toots from Feathercrown@lemmy.world
Needs more AbstractSingletonBeanProxyFactoryDefaultImplementation
=> More informations about this toot | More toots from crispy_kilt@feddit.de
XHR boom. Sue me :)
=> More informations about this toot | More toots from DmMacniel@feddit.de
OP is dead now. Are you happy?
=> More informations about this toot | More toots from Alexstarfire@lemmy.world
Yes!
=> More informations about this toot | More toots from lord_ryvan@ttrpg.network
I regret nothing!
=> More informations about this toot | More toots from DmMacniel@feddit.de
id throw away all of these if they aren’t struct definitions, which they aren’t.
=> More informations about this toot | More toots from JoYo@lemmy.ml
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 notepad or vim can retire soon
=> More informations about this toot | More toots from Boomkop3@reddthat.com
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
=> More informations about this toot | More toots from Kraiden@kbin.run
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
=> More informations about this toot | More toots from Boomkop3@reddthat.com
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.
=> More informations about this toot | More toots from Kraiden@kbin.run
xml-http-request
=> More informations about this toot | More toots from yogthos@lemmy.ml
XML-HTTP-request?
=> More informations about this toot | More toots from sik0fewl@lemmy.ca
xhr
=> More informations about this toot | More toots from jimitsoni18@lemmy.zip This content has been proxied by September (ba2dc).Proxy Information
text/gemini