Recent submissions

Comment · 23 hours ago
Improper for sure. Illegal? maybe. It should be at least.
Comment · 1 day ago
Criminal negligence usually involves bodily harm or serious risk of bodily harm.
Comment · 1 day ago
I think it’s the mixed terminology that’s causing confusion. Prosecution is for criminal offenses. Lawsuits are for civil cases.
Comment · 3 days ago
OMG $79 more! That ruins everything!
Comment · 3 days ago
I believe you. But Apple has a history of deprecating MacBook Pro after about 7 years
Comment · 3 days ago
It's getting more average every day. QED.
Comment · 3 days ago
You will if you use macos and want to stay supported. On the other hand, being an M1 puts you squarely in Asahi supported territory.
Comment · 4 days ago
The more you people keep harping on this ultra robust backup strategy, the fewer everyday average people are actually even going to attempt a backup.
Comment · 4 days ago
The 2 and 2+ were concurrent.

The 2e, 2e enhanced, 2c, 2c+ and 2gs were concurrent.

I didn’t bother with Mac because I got tired of writing all the things.

Comment · 4 days ago
As others have said, the pro is a different mask set.

But you are right, they do bin. You can get versions of the cpu with different core counts for this reason.

I’m only seeing this with the pro and max though.

Comment · 4 days ago
And you think 1 is better.
Comment · 4 days ago
Are you kidding? When have they not? Apple II, II+, IIc, IIc Plus, IIe (also //e), IIe enhanced, IIGS. All sold concurrently.

They’ve always been this way.

Comment · 7 days ago
This has never not been true. There are always hand wavy axioms at the bottom.
Comment · 8 days ago
I fully agree it’s harder to read. I do chip design and I feel like formal is more common in this area, but I generally restrict it to very simple properties that are easy to understand without having to mentally solve a sudoku puzzle.

It’s to easy to write an assertion that looks like it checks what you want it to, and gives you a false confidence when it passes, only to figure out after a field failure that it wasn’t checking what you thought at all.

But I’d pay for a commercial set of properties and assertions that had guarantees, and not worry about their complexity. For something standard like cache protocols and bus protocols.

Other cases it needs to be pretty straightforward to grasp by a peer reviewer in minutes, or it’s not worth it.

But when you can hit the sweet spot, a set of easily understood properties (or complex but trusted properties), formal can save massive amounts of time.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton