amaterasu

I love the way they buried the “we are no longer supporting an entire operating system” in a small missing tick, half way down the page…

I'm trivialising, but a lot of software in medical devices is turning a GPIO pin on/off in response to another pin, then announcing that it did so. The piece missing from the article is that the assumed probability of software/firmware (or anything really) failing is 1.0. Everything is engineered around the assumption that things (_especially_ software) WILL fail and minimising the consequences when they do. LLM's writing the code will happen soon, it's a GPIO pin control after all. LLM's proving the code is as safe as possible and that they have thought about the failure modes will be a while.

The co-leads on drafting the code are rather interesting:

> Drafting of the code was co-led by Digital Industry Group Inc. (DIGI), which was contacted for comment as it counts Google, Microsoft, and Yahoo among its members.

Underwriters Laboratories, UL. Look at the back of pretty much any mains powered device and you'll see their mark. They were founded 130 years ago, and test and warrant devices (typically high voltage) to be safe. Security is a new thing for them, but they're well suited to provide the services.

In which shell?

Ignoring the common trope that developers are bad testers (I am, but not all devs are), QA presence allows teams to move faster by reducing the developer test burden to automated regression, and developer acceptance testing only. Good QA can often assist with those tasks too, further improving team velocity. Also, moving tasks to people who specialise in them is not usually a poor decision.

The best way I've found to sell QA to management (especially sales/marketing/non-technical management), is to redefine them as marketing. QA output is as much about product and brand reputation management as finding bugs. IMO, nothing alienates customers faster than bugs, and bad experiences result in poor reputation. Marketing and sales people can usually assign value to passive marketing efforts, and recognise things that are damaging to retention and future sales.

If I was a prosumer/hobbyist video equipment company, I'd be terrified about what Apple does next. They already have significant penetration into the editing market (both with Final Cut, and codec design), they control a number of the common codecs, and they have _millions_ of devices in the field along with substantial manufacturing capability. The cinema end aren't in trouble yet IMO, but the rest should be concerned...

Some sensors do this internally, unusual though. The rest of the high-end ones apply curves manually in software directly at the egress of the sensor. The reason they don't in all cases is that it complicates black level correction, gamut transforms and demosaic operations (without some assumptions).

For the Australians reading this, Gotham city is a brothel in Melbourne, ymmv on clicking this link at work or school.

Still ending really... There are still travel restriction from metropolitan Melbourne to regional Victoria - expected to end Sunday at midnight. Retail capacity is also limited still, but ramping back up.

Also, there is significant political opposition to this, specifically in the Victorian highlands.

Seconded it not being about safety. In Victoria, traffic infringement revenue is included in the state budget. I'm assuming that the NSW government does the same, so at $344-$457AUD per offence, this is likely just another revenue generating exercise.

Every SoC I've dealt with containing a WiFi core has a dedicated coprocessor (RPU is a common name, depending on vendor) running its' own firmware. So more likely, _that_ core would go funky, then crash. The kernel might have code to recover that, but I doubt it, and it certainly would complain the whole way as you say.

And unlike hdmi 2.0, 1.4 wont have scrambling in, so any termination issues will sing quite well.