this post was submitted on 05 Nov 2026
148 points (99.3% liked)
Fuck AI
8710 readers
1773 users here now
"We did it, Patrick! We made a technological breakthrough!"
A place for all those who loathe AI to discuss things, post articles, and ridicule the AI hype.
Proud supporter of working people. And proud booer of SXSW 2024.
AI, in this case, refers to LLMs, GPT technology, and anything listed as "AI" meant to increase market valuations.
Rules:
- Relevant posts only.
- No bigotry.
- No misinformation.
- No NSFW/NSFL content without being labeled NSFW or being in an appropriately-labeled spoiler tag.
- This isn't a place to talk about the cons and (supposed) pros of AI for different use cases. This is /c/fuck_ai .
- Especially no AI advocacy.
- No AI-generated content. If you want to post examples of AI failing hillariously, there are other communities for that like !ArtificialIgnorance@lemmy.ca .
- Venting is part of the purpose of this community, but don't aim frustration or accusations at other users.
- These rules are a living document that may change in the future.
You can help the mod team by making your reports detailed.
Effective reports:
- "The third image is a well-known anti-semitic trope"
- "Claiming that 'agentic AI' can outperform humans at all jobs is misinformation"
Less effective reports:
- "Breaks rules"
- "Misinformation"
founded 2 years ago
MODERATORS
I have many words, and let's just say none of them good
…single thread
If I had a dime for every time a single threaded process caused a performance issue I’d have enough for a few nice dinners.
It’s 2026, if you can’t effectively multi-thread and learn to parallelize processes i question your effectiveness as a dev. Especially in performance oriented and scalable apps.
Fun fact, someone tried to vibe up something at my work and it totally screwed up threading...
Maybe that's why epic can't do multi thread...
Especially when you're architecting an engine targeting AAA development which needs to eek out every spec of performance they can. Like this isn't them forgetting to use a feature of a language, this is them just not even adding it.
The LLVM also seems like a poor choice. Sure it'll be fine for many but it's still adding overhead and will make it harder to optimize that last 5% to nudge into okay performance. Hardware isn't constantly evolving and being upgraded at the pace it used to.
And actually go look at the syntax of Verse. It's painful to read, which explains why they're pushing LLM driven development so they don't have to see their own monster
It's for gameplay programming, not engine subsystems. These events must eventually be serialized (in the serializability sense, not marshaling) and handled by a single thread for the net code to work. Basically every engine does this (or risk having unreliable networking). The goal of this (last time I looked was when it was announced) is to make it easier to have distributed networking for multiplayer games.
Also building this using c++ and LLVM will result in better performance than any blueprint system can achieve.
We can hate AI and the direction of the engine but don't just assume the devs at Epic are dumb.