"Source code file"
-
Knowing how half-assed they've been deploying Grok a ZIP bomb would probably work on it if they allowed file uploads.
I really want someone to try this and report back. It really does feel like something that could execute.
-
I dunno if you're joking, but yeah there's IDE plugins that do this. GitHub Copilot grabs context from files in your edit history and you can tell it to edit, refactor, "fix" etc. selections. The more complex actions, the less likely to succeed, though.
I assume this is Poe’s Law in action. Elon historically doesn’t understand shit about tech so the commenter is just highlighting something that’s been GA for other tools for years.
-
My sibling in christ, we are trying to code not cause a NATO conflict.
I’d love to see Linus verbally bitchslap the fuckwit. Or physically, that’d be cool too.
-
- Auswitch statement
- V2latile variable
- Goebboolean
- Zyklon C++
- Left shift, Reich shift
- Open and close Parenzer
- Iron Cross-compiler
Thanks I hate it!
-
What do you mean "rest of the project"? Don't you put all of everything into a singular neatly contained file? It's way more optimized that way
With the obscure language I use for work, I do tend to keep each system to a single file, even though includes and modules are supported.
Granted, they are generally between 500 and 5000 lines, and are usually written from scratch.
That being said, there is a 0 percent chance I'm going to be feeding anything I write into Grok.
-
This post did not contain any content.
Cut and paste, what is this 1996?
-
This post did not contain any content.
Wait, so if everyone at xAI does that, does that mean that Grok's own source code was the result of Grok's output?
And then they once again feed that source into Grok?
Dude is destroying his own product. Again.
-
Don't forget to put them all in italics so they execute faster!
No, that makes them slower because theyre leaning into the wind. You want to try to mostly use A's, because they're the most aerodynamic, and anything else should be formatted as subscript to keep code size down and reduce drag. C should be avoided at all costs because it's just going to catch the wind.
-
This post did not contain any content.
That explains a lot, actually.
-
This post did not contain any content.
Hey Grok, take this one file out of the context of my 250,000 line project and give me that delicious AI slop!
-
Hey Grok, take this one file out of the context of my 250,000 line project and give me that delicious AI slop!
Just really fuck up this shit. I want it unrecognizable!
-
Is he using the @ of the handle as part of the grammar of the sentence? Have I misunderstood @ all this time?!?
The first @ was silent, duh
-
Ask for all output in brainfuck.
bf was my first thought, but I would think that would be very easy to parse for computers, and hard for humans. So maybe something that's a lot more verbose?
-
On some platforms if you write @username anywhere then it will act like a tag, or notify the user that you mentioned them, or other similar functionality
He's referring to
This is what everyone @xAI does.
Which Elon probably (maybe?) meant to be
This is what everyone at @xAI does.
-
This post did not contain any content.
Regardless of whether it is truly superior (it isn't, but neither is Cursor, if you think about it), it is actually more tedious to “cut and paste” the “source code file” and then paste back the output.
It is far simpler to just initiate a chat within Cursor, allowing it to identify all the files necessary for context alongside the one being viewed.
-
This post did not contain any content.
No one who legitimately knows anything about computing speaks like this.
He’s truly a moron’s hallucination of a genius.
-
This post did not contain any content.
please don’t use grok.
elon is poisoning the air over memphis with exhaust from the generators that he’s using to power it while using drinking water from the memphis sands aquifer to cool it.
please don’t use grok.
-
This post did not contain any content.
Wait so are they using grok to code grok? No wonder it keeps getting shittier
-
What does the office secrete?
Garbage code. Sadly
-
No, that makes them slower because theyre leaning into the wind. You want to try to mostly use A's, because they're the most aerodynamic, and anything else should be formatted as subscript to keep code size down and reduce drag. C should be avoided at all costs because it's just going to catch the wind.
Conclusive proof that D is faster than C, 2025
