#compilers
and like, comparing the usage of compilers and high level programming languages to uhh

fucking claude
come on. COME ON.
November 8, 2026 at 2:51 PM
Some compilers would recognize specific code fragments and output special optimized code for them and it got noticed because they also applied this to slightly different code leading to incorrect compilation
November 8, 2026 at 11:53 AM
The comment about compilers and assembly is nonsense. Compilers don't make your code into assembly and if it does, it's explicitly to be able to read it!
November 8, 2026 at 4:19 PM
I love when these folks conflate compilers with LLMs. It shows their hand so well.

If LLMs were compilers, they'd get the same answer every single time. But they don't, because compilers are deterministic. LLMs are not.
November 4, 2026 at 11:15 AM
Special delivery
November 5, 2026 at 6:38 PM
In the context of "the analogy", it is true that compilers are deterministic. But, it seems just as important that they produce output based exclusively on the input.
November 8, 2026 at 11:12 AM
ive got good news! most of these compilers can run straight from your machine and they barely use any RAM, and no tokens either!
November 4, 2026 at 7:14 PM
yeah definitely that and it's appreciated. I also meant so much hustle by editors/founders/compilers...assuming they're not vibe-coding the whole thing, which I am seeing a lot of
November 9, 2026 at 3:38 PM
I thought there were other compilers available?
November 6, 2026 at 10:51 AM
😅😅😅

Aye.

1998, the book compilers would've known he'd well fallen off the "legends" list. 🙈🙈🙈

#Celticfc
November 7, 2026 at 11:16 PM
OpenIndiana 2026.10 Released With Updated Tools & Compilers, New Apps

https://www.phoronix.com/news/OpenIndiana-2026.10
November 7, 2026 at 11:00 PM
i think it was tef who said something like “Programmers are like compilers they complain at the first error they perceive“ and like a compiler message what they perceive might not be the actual thing. Anyways I thought it was a great piece
November 8, 2026 at 1:37 AM
Led Zeppelin were Progressive, certainly, but not Prog. The Who were neither, really. I mean they'd been around ages before Progressive appeared on the scene. I think the compilers though 'Oh, Tommy and Quadrophenia are concept albums. Must be prog.'
November 8, 2026 at 3:20 PM
Polyglottal backends are all the rage (currently writing a language called MotL with 3 different compilers—I am not writing the compilers no)
November 6, 2026 at 3:14 AM
I've been thinking about this a lot since Torvalds' recent screed comparing LLMs to compilers (an inherently invalid comparison), and how the "Why do you care what tools people use if they do the job?" point only goes one way. People who say "Ive tried and dont want to use them" dont get any grace.
November 7, 2026 at 10:13 PM
I am old enough to recall 45 minute compile times when using C compilers — back in the 1990s and early to mid- 2000s — for large projects.
I post for the folks who write Rust and are waiting for their compiles to finish.
November 8, 2026 at 9:27 PM
What I want is a new platform that is just a Linux Phone. PERIOD. No store, no "app ecosystem" just a fresh start of a linux kernel and compilers on a phone capable platform. Just enough geek gatekeeping to keep it by geeks for geeks.
This is SUPER serious seeing how explicitly big tech companies have worked to undermine democracies for the US's sake this year alone. It will be incredibly harder for regular people to escape Google's surveillance

Know what is at stake: keepandroidopen.org
Sign the petition: c.org/85bXYmKY9X
November 9, 2026 at 6:31 PM
I was going to mention gcc as a goof, but TIL a thing written in rust called cranelift can be targetted as well.

It's real nifty that compilers are (often) split up into distinct replaceable layers.
November 5, 2026 at 1:21 PM
later on, during a routine coursework requirements review, the assistant department chair decided that with two degrees in linguistics, I didn't really need to take compilers, which is just an extraordinary decision in retrospect lmao
November 7, 2026 at 6:17 AM
It’s so precise you don’t even have to look at the compilers output!
November 6, 2026 at 4:16 AM
when they try the "Ok so you must reject compilers too, and write in assembly?" gotcha on one of the worst people they could have tried it on
Hinatwt Solo Leveling: Sinister Smile
Alt: Hinatwt Solo Leveling: Sinister Smile
static.klipy.com
November 9, 2026 at 9:41 AM
Deep Learning Compilers: Architecture, Optimization, and Empirical Characterization

#CUDA #DeepLearning #DL #Compilers

hgpu.org?p=31472
Deep Learning Compilers: Architecture, Optimization, and Empirical Characterization
As deep learning (DL) models become increasingly complex and hardware architectures grow more heterogeneous, DL compilers play a critical role in optimizing computational efficiency and enabling sc…
hgpu.org
November 8, 2026 at 8:33 PM
I knew with this post being on r/ClaudeCode, there would be some absolute gems of takes like this fucking nonsense here.

Compilers didn't learn to write machine code on their own via statistics. They were engineered to take specific inputs and produce specific, well understood outputs.

Dipshits.
November 8, 2026 at 10:24 PM
iirc, you can’t require an error for all infinite loops with no side effects because detecting infinite loops is the halting problem, which turing proved is undecidable

but compilers have implemented heuristics to detect and emit diagnostics for **some** infinite loops with no side effects
November 9, 2026 at 10:20 PM