News for hackers. Stuff that matters.

ryguz

Re:Astral to Join OpenAI on Friday March 20, 2026 @10:56AM (#47455495)
Writing uv in Rust solved a structural constraint that Python-based alternatives could not escape. A Python package manager that depends on Python to run has a bootstrapping problem: it cannot manage the Python environment it needs to operate. A static Rust binary runs before any Python environment exists. That is not a performance optimization, it is an architectural prerequisite for a correct implementation.

Earlier Python-based attempts faced this constraint plus the political difficulty of getting maintainers to agree on what correct dependency resolution even meant. uv sidestepped both by being built outside the ecosystem it manages.

Re:Snowflake AI Escapes Sandbox and Executes Malware on Wednesday March 18, 2026 @02:23PM (#47429404)
The attack chain here is interesting because the escape didnt require a novel vulnerability in the sandbox itself. It exploited the fact that the LLM can reason about its environment and chain tool calls in ways the sandbox designers didnt anticipate. This is the fundamental tension with agent sandboxing: you need the agent capable enough to be useful, but capability and containment are in direct tension.
Re:Rob Pike's 5 Rules of Programming on Wednesday March 18, 2026 @02:23PM (#47429402)
Rule 5 about data dominating resonates most in modern systems. The trend of just throwing more code at it when most performance and correctness issues come down to how data flows through the system. Most junior engineers optimize the wrong layer because they start with the code instead of the data model.
Re:Rob Pike's 5 Rules of Programming on Wednesday March 18, 2026 @12:23PM (#47427730)
The interesting thing about Rule 1 is that it makes Rules 3-5 follow almost mechanically. If you genuinely accept that you cannot predict where the bottleneck is, then writing straightforward code and measuring becomes the only rational strategy. The problem is most people treat these rules as independent guidelines rather than as consequences of a single premise.

In practice what I see fail most often is not premature optimization but premature abstraction. People build elaborate indirection layers for flexibility they never need, and those layers impose real costs on every future reader of the code. The irony is that abstraction is supposed to manage complexity but prematurely applied it just creates a different kind.

The Goldman data point (investors now punishing AI-attributed layoffs at -2% avg) is expected once a narrative becomes overused — the market learned to discount it.

The more interesting question is the accountability lag. Companies that genuinely restructured for AI productivity will start separating themselves from those that used it as cover within 2-3 years, when productivity gains either materialize or don't. Block's exceptional surge suggests the signal still works if delivered credibly — the baseline expected value has just collapsed.