arghwhat

ecosystem != UI

Buttons sized to be hit by your physical thumb and buttons sized to be hit by a tiny high-precision cursor are very different things.

I am sitting on a macbook pro with the vertical tab pane open in chrome, with 12 tabs. The outer joint of my thumb covers the entire list, in both width and height. A touch-friendly version of that would be humongous in comparison.

Looks just as notchy as they've always been.

Heh, no, it's soldered.

If you throw enough money at a sufficiently skilled technician it can be done, but no M.2 slots in sight here.

Doesn't change that it isn't accurate.

In Scandinavia, lack of air condition in homes vs. presence in cars has nothing to do with carbon programs.

What options become standard in cars, and what options are cheap to implement in cars (adding a bit more piping during assembly), follow an entirely different market dynamic than the retrofitting homes (most houses are either pre-WW2 or from a boom in the 50's to 70's) with air conditioning to handle what used to be very short bursts of heat.

Not only did weather not demand it, old brick houses have significant thermal mass and during sudden heat waves you'll often find the inside to already be noticably cooler.

It's being considered now both because weather got weird and our construction went so far in energy efficiency that while new construction barely require any energy to heat in the depths of winter, they become literal ovens in peak of summer.

You are mixing unrelated requirements together here.

> The CRA requires manufacturers to notify actively exploited vulnerabilities and severe incidents having an impact on the security of their product with digital elements. They need to submit an early warning within 24 hours of becoming aware, and a full notification within 72 hours.

These deadlines are entirely unrelated to the availability of security fixes and delays in deliverying them.

I do not believe that any corporate lawyer would think that. It does not read like that in neither plain english nor legalese.

Maybe the misunderstanding stems from the related common misuse of "as soon as possible" as "immediately"?

A corporate lawyer would, however, always suggest to minimize/reduce/delay any legal obligations so as to minimize risk of liability, regardless of whether said obligation is easy to comply with or not.

nit: "without undue delay" does not mean "immediately" under any legal interpretation, only that the timeline should not be longer than necessary. This leaves a lot of wiggle-room in favor of the manufacturer, and mainly rules out that they go "eh, we'll look at all these in half a year maybe".

As long as they start the process and it is not absurd from an industry standards perspective, they should be good. They can have slow processes, including being a good bit slower than their peers, without running afoul of "without undue delay".

Eh. WebKit, Blink, Gecko being the big ones, supporting Windows, Linux (and alikes — maybe one would consider Android separate in this context) and Darwin (in this context iOS/macOS is the same). Mostly 1:1.

The thing is that it's still just a library, it just happened to be pre-installed. CGImage is just a helper in the Core Graphics library, not some magical "native"/"core" functionality in the OS that would be different than any other library with the same features.

An equivalent library for Linux (glycin for example), or per-format libraries like jxl-rs, are not "included in the OS", and tend to be the very same libraries one would use for Windows. If that does the trick on most platforms, then why have the maintenance burden of doing something different on macOS if all it does is save a few bytes on disk?

From Google's perspective, they would likely not want Chrome for macOS to gain support for jxl as the sole platform anyway, even if they are using CGImage and could decode it that way...

That is not what relative privation fallacy is. The topic at hand is repeated exposure to low radiation does, I gave examples or negligible to high dosages. Disagreement does not make something a fallacy.

Twofold response:

1. It was not directly part of my claim, but yes releasing "toxins" as a binary concept has to be okay because the world, nature and ourselves naturally releases toxins. Irresponsible, excessive or unnecessary release is what matters.

2. In the airline case, it is not the airline releasing anything. It is cosmic rays and solar flares, which you went closer to. The airline should give a heads up in case this information evaded you, but it's the sun you'd need to sue. You'll have to get in line behind all the skin cancer lawsuits it's dealing with though.

A beach body guard has a massively increased risk of skin cancer compared to an office worker. You can, at most, ask for a shade for your watch tower or complimentary sunscreen.

Even for coal and oil powerplants for example, the right thing to focus on is getting rid of it, not extracting ongoing damages. Wind, nuclear, sun.

For flying, in either come up with a viable way and of radiation shielding passenger planes so it can be pushed for policy, or don't fly. Also don't go to very high altitude locations also carry increased risk.

As for contamination zones, that's specifically something the one to blame will have to keep paying to manage and clean up. Their fault, their bill. But even with all that it still ends up being what takes the fewest lives, due to just how much work for society that one plant did vs. any alternative.

I see the good intent but I cannot agree on several points.

First point is that even though radiation can cause cancer, radiation is part of life. If my basement has higher levels of radon, who should compensate me? What about the radiation exposure from requested x-rays, or food?

Second is responsibility. If I decide to fly a lot, my increased radiation exposure is not the fault if the airline. It's not their fault that the atmosphere is less protective up there, and everyone flying is equally exposed. Now if they could prevent the radiation they preferably should, but until then their responsibility is disclosure of this information to allow informed decisions. Can't blame the ocean for being wet.

Third is that by that logic, it very much has bearing whether "wind turbines kill people", as it implies that every fractional possible cause of harm must all be measured and pay in proportion to their possibility of damage.

There would be no way to even start. However, I do agree that when accidents or negligence/malice is involved, it makes sense that the actor spends energy cleaning up. For example, the biological harm to people in Fukushima was practically non-existent, but the short-term the economic and social harm was there and was entirely avoidable. Damages should be paid.

(Of course, windmills don't kill people, point is that wind, nuclear and solar is so harmless that the only thing we're looking at is differences in construction-related workplace accidents, which are a bit higher with windmills and lower with solar.)

Yes, but terminal escape sequences are a very, very small surface. It's just a few opcodes like "wipe screen", "switch to buffer B", "move to X,Y". All process output regardless of whether it is a terminal escape sequence or regular text just navigate and update the screen "cells", and in, say, alacritty this will be in boring, non-unsafe Rust.

For comparison, the surface exposed by your browser rendering this text controlled entirely by an adversary (me) is considerably greater as it also interacts with the style system, content reflow, javascript engine (even for non-javascript websites), etc.

People understand that such "reverse hacking" can happen when their browser connects to any site (including all the indirect connections from dependent resources), right? Or when resolving any domain name? Or when even just pinging an IP?

The risk is far, far lower than browsing the internet. Unlike the massive surface of a browser and all the libraries and processes it is comprised of, the OpenSSH client is a tiny, with a singular purpose, contained in a small and very well-vetted codebase.

From the perspective of connecting to a foreign network service, the OpenSSH client is about the safest thing you can possibly use. Note the use of relative words here - not claiming it is 100% bug-free.

(The main caveat is that you can manually configure the client to do unsafe things, like writing a configuration by hand that enables X forwarding or agent forwarding by default for any host - but you can also actively disable sandboxing in your web browser or run everything as root, and we will never be able to stop you from actively making things insecure.)

Large objects (≥ 32 KiB) does not use these categorized arenas, they instead allocate an integer number of 8KiB pages from a heap.

Also note that drivers are made far harder than screws, so it will take many screws turned rivets before a driver becomes said artisinal hole punch.