javawizard

Wait until you get into developing your own PCBs and discover the BK7238 for $0.81 :)

Figure out how many humans are required to make the decisions, then hire that many humans and have them do it.

I swear this is like a restaurant chain complaining that they shouldn't be required to follow foodservice regulations because of how much money it costs them at scale.

Really? It's better than Opus 4.8, that's the point.

When they release new versions of Sonnet, no-one expects them to be better than Opus.

LIN bus isn't masterless though, if I recall correctly.

That's the nice thing about CAN: every node is equal, and every node can send a message whenever it wants. As far as I know, LIN doesn't do that: you have one node on a given LIN network that initiates all communication, much like I2C, and the most other nodes can do is reply.

It's fine for what it is, of course, it's just missing some things that I think make CAN really neat.

I really, really wish that CAN had caught on more for sensor networks in the hobbyist community.

It's so much nicer than I2C in so many regards: much longer range, masterless (any node can talk directly to any other node), packet prioritization built-in, deliberately designed to be more or less impossible to wedge, possible to do IC-to-IC on a board without transceivers by using a shared open-drain bus (like I2C, but with only one wire!)... and plenty more.

Really the only downside to CAN is that the spec requires timing that's tight enough that everything has to have a crystal on board. Ah, to have an alternate reality where CAN's timing requirements were relaxed enough for that not to be a requirement and it had caught on as the IC-to-IC interconnect standard instead of I2C...

> HuggingFace got hacked by an AI. What stuck out to me was the guardrail asymmetry. The attacker had no constraints, but HF's response ran afoul of the abuse guardrails, forcing them into an unplanned switch to local models.

This, to me, is the more interesting bit of the article.

I don't really know what a good solution looks like, but yeah, that's annoying.

I just had this happen today. It was indeed a segfault.

From what I could tell it looked like it was in JS code that had been JIT compiled. I haven't attempted to troubleshoot further beyond setting all my future Claude Code instances to pipe their stderr to disk so that I don't lose the stack trace next time.

Please read the article. This post is over a month and a half old.

Lot of armchair quarterbacking going on, on both sides. I'd love to hear an actual farmer weigh in on this.

Anyone in the room care to volunteer?

At least AES membership gets you free access to all of their standards, which is more than can be said for IEEE.

Source: I'm a card-carrying AES member.

Oh! You did. I just saw the two in adjacent sentences and assumed you were referring to the Netflix CEO and had mixed up his name.

Nothing to see here, move along...

> This is what Netflix has always been advocating for. Reid Hoffman also wrote the book The Alliance

I think you might have Reid Hoffman (founder of LinkedIn) mixed up with Reed Hastings (founder of Netflix). :)

They didn't say that HN is turning into Reddit, they said that the conversation quality has gone to shit.

I don't agree with that statement universally, but I have to say I do when it comes to this article. I came here hoping for substantive discussion from those who'd had a chance to try it out; instead what I got was a seemingly endless stream of venting. There's a place for venting - and plenty to vent about with the state of AI nowadays - but to borrow from the HN guidelines you linked, it does very little to gratify my personal intellectual curiosity.