129
you are viewing a single comment's thread
view the rest of the comments
[-] WhyEssEff@hexbear.net 32 points 7 hours ago* (last edited 7 hours ago)

lets add full seconds of latency to malloc with a non-determinate result this is a great amazing awesome idea it's not like we measure the processing speeds of computers in gigahertz or anything

[-] WhyEssEff@hexbear.net 21 points 7 hours ago

sorry every element of this application is going to have to query a third party server that might literally just undershoot it and now we have an overflow issue oops oops oops woops oh no oh fuck

[-] WhyEssEff@hexbear.net 17 points 7 hours ago* (last edited 7 hours ago)

want to run an application? better have internet fucko, the idea guys have to burn down the amazon rainforest to puzzle out the answer to the question of the meaning of life, the universe, and everything: how many bits does a 32-bit integer need to have

[-] WhyEssEff@hexbear.net 16 points 7 hours ago* (last edited 7 hours ago)

new memory leak just dropped–the geepeetee says the persistent element 'close button' needs a terabyte of RAM to render, the linear algebra homunculus said so, so we're crashing your computer, you fucking nerd

[-] WhyEssEff@hexbear.net 18 points 7 hours ago* (last edited 7 hours ago)

the way I kinda know this is the product of C-Suite and not a low-level software engineer is that the syntax is mallocPlusAI and not aimalloc or gptmalloc or llmalloc.

[-] WhyEssEff@hexbear.net 15 points 7 hours ago* (last edited 7 hours ago)

and it's malloc, why are we doing this for things we're ultimately just putting on the heap? overshoot a little–if you don't know already, it's not going to be perfect no matter what. if you're going to be this annoying about memory (which is not a bad thing) learn rust dipshit. they made a whole language about it

[-] WhyEssEff@hexbear.net 14 points 7 hours ago

wait is this just the e = mc^2^ + AI bit repackaged

[-] Llituro@hexbear.net 16 points 7 hours ago

if you're going to be this annoying about memory (which is not a bad thing) learn rust dipshit. they made a whole language about it

holy fuck that's so good data-laughing

[-] T34_69@hexbear.net 7 points 7 hours ago

t the syntax is mallocPlusAI and not aimalloc or gptmalloc or

I-was-saying

[-] WhyEssEff@hexbear.net 8 points 7 hours ago* (last edited 7 hours ago)

if they're proposing it as a C stdlib-adjacent method (given they're saying it should be an alternative to malloc [memory allocate]) it absolutely should be lowercase. plus is redundant because you just append the extra functionality to the name by concatenating it to the original name. mallocai [memory allocate ai] feels wrong, so ai should be first.

if this method idea wasn't an abomination in and of itself that's how it would probably be named. it currently looks straight out of Java. and at that point why are we abbreviating malloc. why not go the distance and say largeLanguageModelQueryingMemoryAllocator

[-] T34_69@hexbear.net 6 points 7 hours ago

I might call it like, malloc_ai so it's like, I INVOKE MALACHI lol

[-] WhyEssEff@hexbear.net 7 points 7 hours ago* (last edited 7 hours ago)

snake_case is valid, I’m just operating on the assumption that these rubes want it to be stdlib-adjacent

[-] T34_69@hexbear.net 3 points 3 hours ago

Well come to think of it, we did find out that certain snakes are standard lib-adjacent in disguise warren-snake-green

this post was submitted on 18 Oct 2024
129 points (100.0% liked)

technology

23238 readers
239 users here now

On the road to fully automated luxury gay space communism.

Spreading Linux propaganda since 2020

Rules:

founded 4 years ago
MODERATORS