Hm, this seems like a difficult argument to support.
We shouldn't have laws because "the enemy" doesn't have laws, and thus they are moving faster?
Okay, so "the enemy" or "national security" becomes a reason that can be cited for any reason, at any time, to abolish or ignore any and all regulation?
In what world is that NOT the slippiest of slopes?
Technically you could say that, but the entire server runtime is written in Rust. V8 is just the embedded JavaScript engine. By that logic, every Node.js or Deno app would be "C++ powered" since they all use V8.
Clearly they’re referring to deepmind. I don’t have an opinion on how accurate this is, but feigning ignorance doesn’t help further discussion or reduce echo chambers.
I earnestly can't anticipate what specific information-diet someone could have where they would so strongly assume that Google Deepmind (of all the various AI companies) is a clear and sole foil to Grok that they would assume anyone who didn't share that perspective to be feigning ignorance in bad faith.
Where-ever you're having these discussions where it's entirely unfamiliar to me (and evidently others). (I don't say this with scorn or malice!)
On the greater topic of "bias", it's kind of meaningless. There's correct answers and there are incorrect answers, and "bias" refers to some tendency away from an assumed default distribution. Randomly-generated strings might be the only "unbiased" response. This is really more a difficult epistemic question, and I'd prefer something that is biased towards what's most likely to be true (e.g. Wikipedia > someones Livejournal).
Given Grok has been intentionally made to generate text praising Hitler, and I have very very high confidence that Hitler actually sucks, I have very very low confidence in the ability for the Grok program to reliably generate text that's worth reading.
> Author's Note: I had a lot of fun writing this one! Please do not get too worked up in the comments. Most of this was written in jest. -Ber
Are you sure it's not just misalignment? Remember OpenClaw referred to lobsters ie crustaceans, I don't think using the same word is necessarily a 100% "gotcha" for this guy, and I fear a Reddit-style set of blame and attribution.
Sorry, I'm not connecting the dots. Seeing your EDIT 2, I see how Ber following crabby-rathbun would lead to Ber posting https://github.com/matplotlib/matplotlib/pull/31138 , but I don't see any evidence for it actually being Ber's bot.
Meanwhile GPT-5.3-Codex which just released recently is a huge change and much better. It now displays intermediate thinking summaries instead of being silent.
There's one really confusing thing in Codex CLI from my perspective. How do I make it run unsandboxed but still ask me for approvals? I'm fine with it running bare on my machine but I like to approve first before it runs commands. But I only see how I can configure to have both or none. What am I missing?
Thanks! That helped. Really strange though, that the slash commands inside the CLI do not allow for such a detailed configuration. It allows for the sandbox and approvals options but there's only "default" and "just allow everything" while the CLI flags or the config.toml allows for more nuanced options.
Yes a human can hack together a compiler in two weeks.
If you can't, you should turn off the AI and learn for yourself for a while.
Writing a compiler is not a flex; it's a couple very well understood problems, most of which can be solved using existing libraries.
Parsing is solved with yacc, bison, or sitting down and writing a recursive descent parser (works for most well designed languages you can think of).
Then take your AST and translate it to an IR, and then feed that into anything that generates code. You could use crainlift or whatever it's called, you could roll your own.
Afaik the Linux Kernel strongly depends on GCC extensions and GCC specific behavior, so maybe that's why this is such an interesting part? Also extensions like inline assembly seem wildly complicated to add to an existing compiler WHILE replicating the syntax and semantics of another compiler (which has a different software architecture).
> Parsing is solved with yacc, bison, or sitting down and writing a recursive descent parser (works for most well designed languages you can think of).
No human being writes a recursive descent parser for "Linux Kernel C" in two weeks, though. And AFAIK there's no downloadable BNF for that you can hand to an automatic generator either, you have to write it and test it and refine it. And you can't do it in two weeks.
Yes yes, we all know how to write a compiler because we took a class on it. That's like "Elite CS Nerd Basic Admission". We still can't actually do it at the cost being demonstrated, and you know it.
So did most of us, join the club. What you can't do is write such a compiler for $20k if you want to put food on the table, or do it in two weeks (what it costs to buy your time currently until AI eats your job). And let's be honest: it's not going to build something of the complexity of Linux either. Hobby compilers run hobby code. Giant decades-old source trees test edge cases like no one's business.
I don't really get what you're arguing. Yes, battle hardened compilers are great. No, I can't write one in two weeks, and neither can a group of AI bots.
The result is a heap of technical debt so unmanageably large that it's almost an exponential cost to keep adding to it.
reply