crote

Yes, but it's no different from the QR codes already present on many consumer products. In fact, it is easier to spot, as either a cashier (or someone at a self-checkout) is likely to notice that there's a sticker over the barcode and get suspicious that there's some kind of fraud going on.

This is already the case. Virtually every single food product comes with an expiration date label - which includes some kind tracking. You pretty much need to have that to do any kind of sensible recall when there's yet another poop lettuce outbreak. Looking at my pantry it usually seems to be include kind of lot number, time of production, and/or production line identifier.

I reckon they already have a pretty reasonable idea of which store it ends up going to, and with just-in-time resupply a pretty reasonable bound of when it will end up having been sold. Look at the overlap of a few dozen products and it should be quite easy to reduce the number of people who could've bought all of them to just you.

The QR codes just make this more explicit, and slightly easier to track. You're not wrong, but at least this time we could get, say, automated warnings in the Walmart app of a recall on something you bought out of it.

Because the consumer has to be able to trivially scan it with their smartphone and get useful information out of it. In reality, that means it has to be a valid URL you can visit with a web browser, as forcing literally everyone to install a proprietary URN-handling app is a dealbreaker.

The whole point of it is that you can just say "scan the barcode with your smartphone to find out if your product is part of this recall".

On-demand printing. It's how expiration dates are currently already being printed on products during production. The only difference is that it goes from "put it literally anywhere" to "put it inside the space intentionally left blank".

And that's exactly why they went with QR codes. The 2D barcode for checkout just contains a valid URL in a well-known format, so it can do double-duty as link-providing QR code for customer information. And because QR codes can store a lot of data, adding the batch information from the current tracking-only Datamatrix is trivial.

There will be no "wrong" barcodes to scan, just redundant ones for legacy devices.

> People don't do this because it leaves tons of money on the table.

In my country I literally got a letter from the government if I could please file my taxes, because they believe the automatic deductions are too high so I am likely owed a back payment. In a previous year (I am not very good with non-timing-critical paperwork) they even called me on my personal cell to inform me about something similar.

The slogan of our tax collection agency is "we can't make it more enjoyable, we can only make it easier". If you're a regular employee and your taxes - deductibles or not - are a hassle, then that's 100% a political choice.

> AI-generated images can be indistinguishable from ones created by humans.

The people who make basic posters and menus by prompting an AI are neither using the proper tools nor the proper prompts to reach that level of quality.

> I also doubt most people care if something was AI-generated

A lot of people hate AI, even if only because of what it represents - which is giant tech companies completely overhauling your day-to-day life for a few cents of profit.

> They only care about the end result, which for AI-generated content can be as good or better, faster, and cheaper than what many if not most professional humans can do

Exactly, and the AI-generated content is 99% obvious slop. Could a skilled professional have used AI to make something decent-looking? Yes, but that's not what is happening. What we are actually seeing is someone who has never used AI prompting it for "a poster" and grabbing the first output. It doesn't even have the quaint look of work created by an enthusiastic-but-untrained amateur, it just looks plain bad.

If all AI output looked amazing and nobody could ever tell - or simply didn't care - then we wouldn't be seeing articles about "AI fatigue", would we?

Which is considered a Really Bad Idea because tags aren't immutable, so there's absolutely zero guarantee that it'll point to the same commit a few months from now.

The GitHub Actions ecosystem found out the hard way, through some rather high-profile compromises. They hotfixed it by adding "immutable tags" to their platform, and are now working on adding a lockfile to... easily reference a commit hash.

Dealing with potentially-hostile hosts is quite common, actually. See for example how most Linux mirrors work, or Subresource Integrity with HTML.

Turns out securing a service to transfer a single hash is a lot easier than securing a service to transfer gigabytes of data.

Even if I don't fully trust Github, it is still incredibly convenient to be able to upload my code there and then send someone an email telling them to fetch commit `123abc` from some repo link. As long as my email isn't compromised, that should be secure.

That doesn't make a difference: with sha1 a malicious change in content will still result in the same content hash, so the signature will still be valid, and the commit hash will still be the same.

That's today. You have to think about what the industry is going to look like in a decade.

Building a DRAM company from scratch is hard, expensive, and risky. You're burning a fortune to get started, and the result is a commodity product. But the AI bubble allows CXMT to have terrible yields, sell a legacy product, and still make a healthy profit! This is literally a once-in-a-lifetime opportunity to catch up.

And yes, right now that means selling DRAM for 10% below the crazy AI-inflated prices the incumbents charge. But sooner or later either demand will drop or supply will catch up. CXMT, like many other Chinese companies, is undoubtedly willing to operate at razor-thin margins to increase market share. Either the other manufacturers move down as well, or they'll be made irrelevant by CXMT stealing all their customers.

The thing is, who's going to pull the cart? Giving stewardship to a nonprofit is perfectly fine from an IP perspective, and they'll have no trouble finding someone to herd some bugfixes, but what's going to happen when significant refactoring is needed to add support for C++26/29/etc?

Having your resident compiler expert upstream the occasional patch to keep your legacy product from dying is one thing, but which big tech company cares about this specific compiler enough to spin up an entirely new dedicated team for it? And who's going to choose a mostly-abandoned compiler front-end as a core part of a new product?

Sure, it can be done, but for each individual user defecting to clang must be looking very attractive right now.

A lot of the duck curve can be solved by tiny changes on the demand side. Uranium isn't exactly conflict-free either. Grid storage can also be done with sodium ion batteries or iron redox batteries - even better than the current EV-spinoff lithium ones.

Sure, solar isn't free, but most of the problems it faces aren't exactly insurmountable. In fact, we are already seeing those solutions being deployed in the world - mostly for economic reasons.

Okay, let's follow that logic. I am willing to bet $1 that there will be construction delays and that there will be cost overruns. How many millions are you willing to bet that there will be absolutely zero delays and overruns?

If those reactors are so fantastic, surely you wouldn't hesitate at a chance to get some free money - no matter how little?

So are wind turbines. "Deliverable by truck" in this sense means "physically fits on a closed-down highway", not "you'll randomly pass it on your commute".

You're missing the fact that a submarine tends to be submerged in the ocean, and that it is fueled with highly-enriched uranium.

Naval reactors and civil reactors look roughly the same at first glance, but as the folks at Three Mile Island found out the hard way, there are some rather crucial differences.

Where would that new life come from? As far as I am aware, there isn't exactly a thriving community around it which has been begging for a source release for ages, and with Clang and GCC there hasn't been a shortage of open-source C++ compilers either. And it's not exactly like the C++ ecosystem as a whole is booming, with it not having any answer to the memory safety problem.

From what I can tell this is just some retiring guys who want to make sure their life's work isn't lost to history, and who want to avoid screwing over their handful of remaining customers. Realistically, the best you can hope for is probably the occasional bugfix, and other open-source compilers scavenging it for a handful of useful clever ideas.

In other words: the CAB members would distrust the CA because the CA would be in violation of their individual root store policies, specifically the "you must follow the rules set by the CAB" part.

That doesn't sound like much of a contradiction to me: anyone already using standard ACME tooling can change to their new CA with a trivial configuration change - provided their standard ACME tooling is well-maintained enough to include a 5-year-old protocol extension.

The problem is that "can loiter over an area" and "SR71-like" are fundamental contradictions.

The whole point of the SR71 is to be stupidly fast, to the point of being impossible to catch. It could outfly missiles, and the mission was done and over by the point anyone could scramble a proper defense. Have it fly circles over a target and you're negating its one main unique selling point.

Want to loiter over a target? Use an RQ9. Want an impossible-to-stop snapshot camera? Use a satellite. So what's left for the SR71? I guess there are some missions where 1) you don't have air superiority, and 2) the target can hide in time from well-known satellite orbits, but 3) the target can't hide with 15-minute warning from a plane - but are those really common enough to justify the massive investment it'll take?

> we can't make a saturn 1 any more because the tools were destroyed and it would be ludicrously expensive to make an F1 engine

The bigger problem there is that we don't have the people any more.

The Rocketdyne F1 was the pinnacle of hand-crafted engineering, with each engine being slightly different and the people having to account for those differences during assembly. It has a whole bunch of complicated welds which require a lot of tweaking, adjusting, and literally days of welding work? Neil's got to go to the moon, so you better get to it!

Those highly-skilled highly-specialized engineers don't exist any more, and for a good reason: with CNC and robots we can achieve far superior results for a fraction of the cost. It just requires the designers to make it automation-friendly from the start. Those skilled people retired (and by now died) without a replacement, because the job had become obsolete.

So no, we literally cannot build a new Rocketdyne F1. We can design and build a better F1-like engine, though!

> The sad thing is that in a way the terrorist won.

So did Netanyahu. His far-right policies require an eternal enemy to distract the people and blame for everything going wrong. The October 7 attack definitely didn't hurt his position in national politics.

> Those that actually have to defend themselves, like the US, rather than relying on strong allies

Sure, but are we going to ignore about the US having to rely on its "helpless" allies to provide staging points and cannon fodder for its illegal imperialistic wars? How much of a superpower would it be without its overseas bases?

So you're suggesting that Israel would drop a nuke on a Western country imposing a boycott? Somehow, I doubt it.

"Destroying all the buildings" is already a genocide on its own. In the Genocide Convention this would fall under "deliberately inflicting on the group conditions of life calculated to bring about its physical destruction in whole or in part".

> But we’re much more concerned about the circumstances Jews find themselves in after the Holocaust/WWII.

The problem is that the historical timeline doesn't match up. Zionism started way earlier, and tried to found a "Jewish homeland" in 1820 in New York, and in 1903 in Uganda, and there are literally dozens of other examples throughout history. Even if we look solely at modern-day Israel, it dates back all the way to the Balfour Declaration of 1917. The first settler violence started decades before the Holocaust ever begun.

> I don’t agree with the conflation of Zionism to ethnic cleansing.

How do you propose Zionists could've established an ethnically Jewish country on land already occupied by Palestinians without ethnic cleansing? Why didn't the Zionists migrate to Palestine by integrating in the already-present culture and society, rather than by displacing it?

> They [..] left Gaza.

Sure, if you ignore the part where they kept bombing Gaza, assassinated political leaders, did ground incursions, and blocked it by land, sea, and air.

If Israel wanted a peaceful two-state solution, why did they keep occupying Gaza by turning it into an open-air prison?

Except you shouldn't do the GMT/PST part, because it can lead to people falsely believing that Postgres can handle time zones, leading to silent data corruption when the time zone definition changes - such as due to abolishing DST.

Postgres can only store 1) unzoned local time, or 2) UTC, with optional conversion on read/write.

And that would be fine, if you were getting an hour of their time. If the lawyer spent 10 minutes finding the right template, 10 seconds filling it in, and then 20 minutes proofreading it, then nobody would be complaining.

In reality they'll spend 1 minute grabbing a close-enough template, 10 seconds filling it in, 3 minutes billing you, and 55 minutes double-dipping by doing work for other clients.

Sure, but it's something you can run on the NPU, not something you must run on the NPU. Whisper will run just fine on your CPU or GPU as well - as will the decades of offline speech recognition tools before.

So what's the actual feature? Slightly higher performance? Slightly lower latency? Slightly longer battery life? And that for something most people are rarely - if ever - going to use?