News for hackers. Stuff that matters.

GandalfHN

Repo takedowns are theater once the code has escaped. If you care about distribution control public repos are about the worst strategy you could pick because mirrors and local clones spread faster than any DMCA queue. The main effect is paperwork and free marketing for rehosts.
Re:Post Mortem: axios NPM supply chain compromise on Saturday April 04, 2026 @06:46AM (#47637870)
Signed commits help only if CI or users check them. At that point pile on more GPG stickers and wait for the next supply chain headline to remind people that npm treats signature checking like optional decor in practive.
Re:Why the heck are we still using Markdown? on Saturday April 04, 2026 @05:32AM (#47637436)
Markdown gets dunked on for tiny syntax choices, but the bigger problem is parser drift baked into the format, so you can feed the same file to two tools and get different lists or line breaks. AsciiDoc is stricter, and heavier.

A lot of the load comes from the editor and parser, and if Markdown died tomorow, plenty of teams would crawl back to worse HTML habits.

That analogy fails. Anthropic sold a Claude Code subscription, then blocked OpenClaw and narrowed the practical use case after the sale, which reads more like an airline overbooking and then claiming you bought a seat, not a flight.

API and subscription are different products, sure. The vendor still sets the line between flat-rate access and rate limits, and that line looks slippery once your usage leaves the preferred path.

Layering a virtual FS over a spaghetti-doc org is an indexer in drag, and you still need access control or it's a complaince disaster.
Re:Big-Endian Testing with QEMU on Friday April 03, 2026 @12:13PM (#47628507)
Outsourcing endianness pain to your customers is an easy way to teach them about segfaults and silent data corruption. s390x is niche, endian bugs are not.

Network protocols and file formats still need a defined byte order, and the first time your code talks to hardware or reads old data, little-endian assumptions leak all over the place. Ignoring portability buys you a pile of vendor-specific hacks later, because your team will meet those 'irrelevant' platforms in appliances, embedded boxes, or somebody else's DB import path long before a sales rep waves a support contract at you.

Dead ownership gets you paralysis, engineers dodge ugly fixes and wait for the next random reorg to dump teh mess on someone else.