This Year in LLVM (2025)(npopov.com)
26 points by asb | 0 comments
First screen, captured .
Looks similar
CSS: Unavoidable Bad Parts(matklad.github.io)
109 points by surprisetalk | 65 comments
Migrating Dillo from GitHub(dillo-browser.org)
400 points by todsacerdoti | 199 comments
A news post by Dillo maintainer Rodrigo Arias Mallo explaining why the Dillo browser project is moving from GitHub to a self-hosted server with mirrors on other forges.
Vibecoding #2(matklad.github.io)
113 points by ibobev | 78 comments
Optimizers need a rethink(typesanitizer.com)
132 points by ingve | 139 comments
Related stories
Remembering Johannes Doerfert(blog.llvm.org)
99 points by sdko | 3 comments
An LLVM Project Blog post by Tanya Lattner remembering LLVM contributor Johannes Doerfert.
How to write blog posts that developers read(refactoringenglish.com)
533 points by rbanffy | 148 comments
A chapter from Michael Lynch's Refactoring English offering advice on writing blog posts that software developers will actually read.
Lua: The Little Language That Could(matt.blwt.io)
327 points by mooreds | 183 comments
A blog post by Matt Blewitt praising Lua as a simple, embeddable little language, with examples of why the author likes it.
LinkedIn Larpmaxxing(hereticpleb.vercel.app)
262 points by BurnerBurner | 222 comments
A personal blog post mocking performative LinkedIn culture, describing the author's projects including building a YOLO-based detector for LinkedIn posts.
How I use LLMs to learn complex topics(laurentiugabriel.github.io)
763 points by laurentiurad | 489 comments
Personal blog post by Laurentiu Raducu describing how he uses LLMs to learn complex topics, including building an interactive chip-making game called ChipTycoon.
Why I'm still bearish on LLMs after Navier-Stokes(dank.systems)
426 points by jaykru | 552 comments
Personal blog essay by Jay Kruer arguing LLMs remain overhyped despite headline results like Navier-Stokes, citing poor generalization, reward hacking, and specification costs.