Recent submissions

Comment · 8 days ago
Funny, I’ve had an idea for a similar story for a couple of years. Some key details differ, at least, so it wouldn’t be a direct copy. (Just like you wouldn’t call “The Matrix” a rip-off of “The Terminator” because both involve a dystopian domination of humanity by machines.) But I’ll definitely have to check out this film and/or book sometime.
Comment · 14 days ago
A wheelchair user is a person. Uber’s property is not.
Comment · 14 days ago
I don’t agree with her stance, but it’s absurd to call standing in the sidewalk “disorderly conduct.” I hope the judge sees it that way too and dismisses the charge.
Comment · 15 days ago
Is there a source for the claim that the post was removed per a request from Adobe? I don’t see any pinned comment from a moderator…?
Comment · 18 days ago
Cursor shows “pushes per minute” while Anthropic shows “merges per day.” You can’t directly compare those and say Cursor’s system is more performant. Claude agents could be pushing a similar throughput of changesets into Scion, while some merge agent regularly takes batches and merges them into the trunk.
Comment · 22 days ago
I wonder if this mixes up cause and effect. I've been working on several projects with AI tools to satisfy my intellectual and aesthetic curiosity. But I'm reluctant to share them--to engage with the community--because of the toxic discourse around usage of these tools. "Sure, I could post this cute Go library I worked on with Claude to /r/golang, but people will probably just say 'AI SLOP' and downvote it."
Comment · 1 month ago
They do…? Well, “auto” mode has been default in Claude Code for a couple months now. It’s effectively “safer yolo:” tool calls are inspected by a separate classification system (another smaller LLM, I believe) to approve or deny. And you can always layer on additional sandboxing mechanisms to limit the blast radius deterministically.
Comment · 2 months ago
Seems to be back up now, I've had a couple messages go through successfully in the past ~5min.
Comment · 3 months ago
Huh, that’s what happened. Good thing my company has Bedrock as a backstop for situations like this.
Comment · 3 months ago
Is ChatGPT's interface always this atrociously jittery? Or is it just because this page is getting an HN hug-of-death right now? Every time I try to scroll the whole page goes blank for a few seconds and then re-renders.
Comment · 3 months ago
Is this the GTA 4 trailer?! /s

It’s too bad that ssh doesn’t carry sound. A MIDI-style rendition of the song would really tie it all together.

Comment · 3 months ago
Surprised nobody here nor on the reddit thread caught this one: https://github.com/nahla-nee/wfqueue/blob/main/src/lib.rs#L3...

    unsafe impl<T, const N: usize> Sync for WFQueue<T, N> {}
    unsafe impl<T, const N: usize> Send for WFQueue<T, N> {}
These impls are unsound, because neither constrains `T` to be `Sync`/`Send`. As-written this would let you declare a `WFQueue<Rc<T>, N>` and pass non-atomic-refcount pointers between threads.

The fix is straightforward:

    unsafe impl<T: Sync, const N: usize> Sync for WFQueue<T, N> {}
    unsafe impl<T: Send, const N: usize> Send for WFQueue<T, N> {}
I.e., WFQueue is only Sync if T is Sync, and likewise for Send.

Actually, later on, the code makes a similar mistake, but only for one impl.

    unsafe impl<'a, T, const N: usize> Send for DrivableWFEnqueue<'a, T, N> where T: Send {}
    unsafe impl<'a, T, const N: usize> Send for DrivableWFDequeue<'a, T, N> {}
Comment · 4 months ago
Yes, just like New Coke back in the 80s. Genius 4D marketing strategy.
Comment · 7 months ago
This is correct at the firm level and breaks down at the aggregate level, which is where it gets interesting.

At the firm level, automating away labor costs is obviously rational. But capital in aggregate can't actually rid itself of labor, since labor is where surplus value comes from. A fully automated economy would be insanely productive and generate basically no profit. So the capitalist class pursuing this logic collectively is, without knowing it, pursuing the dissolution of the system that makes them the capitalist class.

You don't have to buy any of that to notice the more immediate mechanism though: AI doesn't need to actually replace workers to discipline them. The credible threat of replacement is enough to suppress wages, justify restructuring, and extract more from whoever's left. That's already happening and requires no AGI.

Comment · 7 months ago
China and/or Russia might have a collection of zero-days they've been sitting on, which they could surreptitiously provide to Iran. Of course, there's attribution risk there, and the opportunity cost of not saving those zero-days for their own later use.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton