New stories

Google has completed the acquisition of the cloud security startup Wiz, marking a significant move in the tech giant's efforts to strengthen its cloud security offerings and capabilities.

I've been deep-diving into diffusion language models this week and I think this is the most underrated direction in AI right now.

The core issue with autoregressive LLMs:

Every major model today (GPT, Claude, Gemini) generates one token at a time, left to right. Each token depends on the previous one. This single architectural constraint has shaped the entire AI industry:

- Models can't revise what they already wrote → we build chain-of-thought, reflection, and multi-pass reasoning to force them to "think before committing" - One forward pass per token → we invest heavily in speculative decoding, KV-caches, and quantization to make generation tolerable - Can't edit mid-output → we build agent frameworks with retry loops, tool calls, and planning layers to work around it - Can't generate in parallel → we build orchestration systems that chain multiple slow calls together

Most of what we call "AI engineering" today is patching around one thing: the model can't look back.

Diffusion LMs flip the paradigm. Start with a canvas of masked tokens, iteratively refine the entire output in parallel. Every position updated simultaneously, the model sees and edits all of its output at every step. Same principle as image diffusion (Stable Diffusion, DALL-E), applied to text.

Why I think the theory actually holds:

1. Parallelism is real, not theoretical. Inception Labs' Mercury 2 (closed-source, diffusion-based) already hits ~1000 tok/s with quality competitive with GPT-4o mini on MMLU, HumanEval, MATH. That's not a benchmark trick — it's a direct consequence of not being bottlenecked by sequential generation. 2. The complexity reduction is massive. If a model can see and edit its entire output at once, you don't need half the scaffolding we've built: reflection prompting becomes native (the model already iterates on its own output), retry loops become unnecessary (edit in place), planning agents get simpler (the model can restructure, not just append). The whole stack flattens. 3. The conversion path exists. You can take an existing pretrained AR model and convert it to diffusion via fine-tuning alone — no pretraining from scratch. This means the billions already invested in AR pretraining aren't wasted. It's an upgrade path, not a restart.

The main limitation today: fixed output length. You must pre-allocate the canvas size before generation starts. Block Diffusion (generating in sequential chunks, diffusing within each chunk) is one workaround. Hierarchical generation — outline first, expand sections in parallel — is another. Ironically, orchestrating that requires an agent, so diffusion doesn't kill agents — it changes what they do.

Honest take: Open diffusion LMs still trail top AR models on knowledge and reasoning at comparable scale. But Mercury 2 shows the ceiling is high, the conversion results are surprisingly good, and the architecture eliminates entire categories of engineering complexity. I think within a year we'll see diffusion models competitive with frontier AR models, and when that happens, a lot of the current tooling (agent frameworks, prompt engineering techniques, inference optimization stacks) gets dramatically simpler or unnecessary.

While researching all this I found dLLM, an open-source library that unifies training, inference, and evaluation for diffusion LMs. It has recipes for LLaDA, Dream, Block Diffusion, and converting any AR model to diffusion. Good starting point if you want to experiment.

Paper: https://arxiv.org/abs/2602.22661

Code: https://github.com/ZHZisZZ/dllm

Models: https://huggingface.co/dllm-hub

What is your opinion?

StackSleuth is a website that provides free tools and resources for developers to analyze their code, including tools for code quality analysis, security scanning, and performance optimization. The website offers a range of features to help developers improve their codebase and ensure their applications are secure and efficient.

Sooko is an AI-powered virtual assistant that helps users manage their daily tasks, schedule appointments, and access personalized information. The platform leverages natural language processing and machine learning to provide a seamless user experience.

The article discusses the upcoming changes to Linux kernel version 6.1, including improvements to the kernel's hardware support, security features, and performance optimizations. It also highlights the introduction of new system call interfaces and the ongoing efforts to enhance the kernel's overall stability and reliability.

The article explores the concept of upfront investment, highlighting how a significant initial investment of time and effort can lead to substantial long-term savings. It emphasizes the importance of strategic planning and automation to streamline workflows and boost productivity, potentially saving thousands of hours of work over time.

The article discusses the potential impact of coding agents, such as ChatGPT, on software development and code quality. It explores the challenges and opportunities presented by these AI-powered tools, and emphasizes the importance of maintaining human oversight and sound engineering practices in the age of automated code generation.

How are you filling your days? A few months ago I was upskilling and prepping for interviews but i've lost all motivation now. I don't want any of this, AI has poisoned the whole ecosystem for good even if one did get back into the game, it all seems like the good old days are over and they were never that great in the first place. I miss having a paycheck more than anything else, even daily standups which I dreaded gave structure and purpose which I am unable to replace.

The article discusses the online presence and activities of a Reddit user named Sentient_Dawn. It provides an overview of the user's profile and interactions on the platform, highlighting their participation in various discussions and communities.

The article discusses the concept of tokenization and how it can be used to create digital representations of physical assets, enabling fractional ownership and increased liquidity for investors.

Hi HN,

I’m a self-coached endurance athlete and long-time user of Intervals.icu. Over the years I’ve gotten comfortable interpreting my own training data (CTL/ATL trends, HRV, fatigue, etc.), but I kept running into a practical problem:

The training plan makes sense when you write it, but real life rarely cooperates.

Bad sleep, work travel, missed workouts, or suddenly having only 45 minutes instead of two hours. In those moments the question becomes: does the planned workout still make sense today?

I built a small tool called PacePartner to help with that:

https://pacepartner.app

The idea is not to replace coaching or generate perfect plans, but to act as a decision layer on top of Intervals.icu.

It connects to your account and reads things like:

training load (ATL / CTL)

HRV / recovery signals

sleep data

planned workouts

upcoming races

You can then ask questions like:

“Should I still do threshold today?”

“I only have 60 minutes — what should I train?”

“I missed yesterday’s workout — how should the week adapt?”

If the workout changes, it can also push the new session back into the Intervals calendar.

What surprised me while building this

Initially I assumed the main challenge would be building a very specialized “AI coach”. In practice the biggest improvement came from simply giving the model good context from the athlete’s actual training data.

Most athletes already have a training plan. The useful part isn’t generating one from scratch — it’s helping adjust it when circumstances change.

Rough architecture

Intervals.icu OAuth integration

Pull training metrics + calendar data via API

Contextual prompt layer grounded in common endurance training principles

Conversational interface (web + messaging)

Still early and very much a work in progress.

Would especially appreciate feedback from:

endurance athletes who use Intervals / TrainingPeaks

people building AI assistants around structured datasets

anyone thinking about AI systems that augment decision making rather than automate it

Happy to answer any questions.

The article provides an in-depth look at the open-source tool ripgrep, a fast and efficient command-line search tool that can quickly search for patterns in files and directories, offering a powerful and flexible alternative to traditional grep commands.

This article explores the concepts of memory pressure, lock contention, and data-oriented design in software development. It provides insights into optimizing system performance by understanding and addressing these fundamental architectural considerations.

A new study by BCG reveals that the overuse of AI in the workplace is leading to a 'brain fry' effect, where employees feel overwhelmed and their productivity declines. The findings suggest that companies need to strike a balance between leveraging AI and ensuring their workforce can effectively utilize the technology.

The article explores the concept of 'just noticeable difference' (JND), which refers to the minimum perceptible change in a stimulus that can be detected by a human. It discusses how understanding JND is crucial for various industries, such as user experience design and audio engineering, to deliver optimal experiences for users.

The article discusses the importance of storage buckets in managing and organizing data, particularly in the context of machine learning and AI projects. It explores the key features and benefits of using storage buckets, including scalability, cost-effectiveness, and data security.