>"Still, the XPS comes with compromises of its own"

Yeah, it runs MS-Windows 11.

Yeah, but the posting said, for Linux, "We are using RDRAND, but it is being mixed in with other entropy being gathered from the system"

If you gather entropy from the environment, like noise from certain chips, start ms time since some last connection, keyboard/mouse movements, etc, that, alone, is random enough for most any use case. And since they are applying that on top of any hardware random number generator, it ensures that it is even MORE random and prevents hardware companies from cheating.

For int'l flights: Amazon Leo is launching next year. Delta is waiting.

And LEO is even easier than GEO since it doesn't have any moving parts. GEO had to rotate to keep alignment. LEO are all using phased arrays.

For existing code in the QA he said leave it be and it's better to fix.

For new code, he's recommending Rust and the advantage he talks about is that it makes the code more maintainable by people. And one thing that every AI coding talk I've seen agrees on is that what makes code more maintainable by people also helps AI and vice versa.

People and AI both have limited attention and memory. The less context necessary the easier it is to evaluate safety.

Another thing not in the summary he touches on is hardware safety. Not just software bugs but also compromised hardware which if your driver is memory safe can also prevent a buggy or adversarial piece of hardware since the hardware is effectively user input.

To balance out OP's selective quoting to avoid people strawman-ing his argument as a fanatic who can't balance risk:

And another +1 Informative! You are on a roll :)

>"The legal jurisdiction for regulating time comes from Article I, Section 8, clause 5 that gives the Congress responsibility to regulate measures, metrics, weights, etc.

Ah, OK. It is a bit terse, saying:

"To coin Money, regulate the Value thereof, and of foreign Coin, and fix the Standard of Weights and Measures"

Playing devil's advocate... To me, it pretty clearly means weights and measures as it relates to coins/money. Otherwise, it would be a separate clause. But one might interpret it as stand-alone. Also, I would consider time a measurement, although which time zone or DST isn't really a measurement, but an offset. We are still using the same units and measurements/values of seconds/minutes/hours/days/weeks/months/years/etc.

Anyway, +1 Informative!

>"It's pretty obvious that official times are related to interstate commerce, so you'll never arrive at the 10th Amendment on this issue."

I don't think it is "obvious" at all. States charging other states taxes or erecting tariffs would be obvious. States not accepting money from other states would be. Natural resources like rivers running through multiple states would be. Time offsets? It doesn't stop, tax, or hinder commerce. Certainly far less than "blue laws", or "dry laws" which were decided to be Constitutional. We already have different time with time zones. One could make an argument far more for time controls than for healthcare or education or hundreds of other abuses of the fed, for sure.

Like I wrote before, if you try hard enough, you can somehow come to a conclusion that just about anything can be grabbed under the Commerce Clause, completely nullifying the 10th Amendment.

>(And frankly if you can't figure out that much, maybe talk less when politics comes up?)

Seriously?

>"Always seemed weird to me that the States were hampered by Congress from deciding on these types of things."

It isn't just weird, it isn't supposed to be that way. See the 10th Amendment (Bill of Rights):

"The powers not delegated to the federal government by the Constitution, nor prohibited to the states, are reserved to the states or the people."

One of the simpler parts of the rule book to understand. And, yet, somehow, it is just ignored. It is pretty clear that time keeping is not delegated to the Federal government by the Constitution (nor is education, child care, health insurance, marriage, speed limits, retirement, gun control, or countless other things). Therefore, the powers surrounding it should be left to the States (or the People, meaning completely uncontrolled by any government). The most popular way around it is invoking nonsense about "interstate commerce clause", effectively trying to find a loophole to make just about anything a power of the Federal government.

Oh well.

That is a compelling argument for more granularity. Of course, the argument against is going to involve things like visiting a friend or family gathering (wedding, funeral, reunion, dinner) or business (with fixed working hours for some service or job interview) in your same State/Province, not that far away, and suddenly you arrive at the wrong time with potentially disastrous consequences :)

I get that might be more expected near a State border or time zone border. But if we end up with a mosaic of different times in non-border areas, it really could get hella confusing.

In any case, the State/Province should be able to handle this far more effectively than an over-reaching Federal mandate (which is the whole reason most power/control should be at lower-levels of government).

>"Ah, like how the Yukon went to permanent DST a few years back and most of BC going to DST this year. Of course in BC, it is up to individual towns etc to decide and along the east they're still debating it."

I hope this legislation does pass. But I also hope that it doesn't get more granular than whole States. Having just parts of States be different (counties/towns/cities) will start to get quite messy and confusing. Nobody will be able to easily keep track of that.

>"Neither the article, nor its source, explain what this site is for, why anyone would go to it, why a website would cost so much... nor anything else."

Yeah, I don't understand why so much money would be needed for just a "web site". More must be going on.

>"I rely solely on my distros to provide updates, including things like kernel firmware. Though I have no idea what the fuck kernel firmware is or does."

The idea is primarily for certain non-open-source firmware, like the BIOS/UEFI, and closed firmware that resides inside controllers that are supported by Linux (like RAID, iLo, higher-end network cards, various controllers, WiFi, etc) to have a central, vendor-neutral site. Various firmware may or may not be part of your distro, depending on its stance on closed-source binary blobs and what type of hardware. As far as I know, no distro has motherboard firmware available has part of their system, just the fwupdmgr program, itself. The actual place that the fwupdmgr downloads from is, indeed, the Linux Vendor Firmware Service (LVFS). It has been around a long time. I have used it several times to check and update the firmware on my various Linux ThinkPads.

>"Marketing was NEVER going to allow units like mi/kWh or km/kWh to be used for flashy new EVs, since those (single-digit!) numerical values would be so much smaller than [ICE] per gallon figures."

I was wondering why they used kWh per distance instead of distance per kWh. The Ariya uses the latter on the dash and manuals, as do most of the postings I see from other EVs. I actually had to convert the article's strange backwards units so I knew what they were talking about.

>"It looks like mainstream EV tech doesn't leave much left on the table for efficiency while also providing amazing performance, and so it takes some questionable choices to make a more efficient EV."

Correct. Motors are already very efficient (80 to 90%) and newer designs can eek out only a few percent more. Weight and areodynamics are all that really remain. Weight is always something you can play with, but the materials start to get extremely expensive when replacing steel (which is cheap and very strong). We understand areodynamics quite well at this point, so that isn't going to get much better without extreme sacrifices in things drivers want- space, visibility, headroom, etc. So EV efficiency is hardly worth worrying about.

What can be improved a lot is range, charge speed, cost, and safety. All of that comes down to battery technology. And there are ongoing improvements there with lots of possibilities. It wouldn't surprise me in 10 years if newer EV batteries double their range (power per volume/weight), double their charging speed, and become far less volatile. All while possibly having even more service life and costing considerably less.