The NASA Vehicle Assembly Building is also a contender.

I’m not sure how many dividing walls there are inside Everett, but the VAB is basically one massive empty skyscraper.

I feel dumber having read that.

Banning a whole country because you disliked a company?

Dealing with stuff that’s ‘almost working’ is often harder than starting from scratch; ask any tradesperson.

They also apparently cannot get their heads around the fact that people might give you a discount if you advertise their brand. Ad-supported pricing has been around for a long time; it’s not some voodoo.

Until the day comes that I get a letter in the mail from the government saying, “Here’s how much you paid in taxes, if you’re cool with that then please disregard”, I will not be satisfied.

NZ does that. More accurately, they email you to tell you that there’s a letter available online - I don’t think they send physical mail by default.

Then they pay any refund straight into your nominated bank account.

Agreed, but “I wouldn’t let him past” sounds a lot like deliberate blocking.

Taking the lane shouldn’t be necessary if there are actual bike lanes and you don’t need to turn. This sounds like deliberately blocking traffic.

It’s also torches and everything after the regulator, which run at much lower pressure. At least in NZ

I think it might be because they’re connected and disconnected regularly so misconnection is a common problem, even with colour coding. Gas work on houses involves actually putting the fittings on pipe and is done by people who should be concentrating more on that rather than on what they’re about to weld/cut.

“Lossless” isn’t the term you want; that refers to not lossily compressing the main data. Lossless compression or storage of media is very rare outside of text and sometimes audio, because it ends up so large.

You want to preserve metadata. That applies regardless of how lossy the data compression is.

I’ve heard flammable gas uses reverse (left hand) thread to prevent cross connection. At least for welding gases in NZ; not sure about natural gas.

Isn’t that fundamentally the idea behind ‘separate but equal’, which has been pretty thoroughly smacked down in the US? It very quickly turned into (always was) separate and not equal.

Doing it in an ironic, performative way for art is one thing, but I’m not sure it’s a great blueprint generally.

I don’t remember if they fully closed the loopholes, but there are inputs that programs cannot catch unless you actually replace the OS.

Here in NZ they do a factory reset on your calculator at the start of every exam.

Even 95% is on the low side. Most residential-grade PV grid-tie inverters are listed as something like 97.5%. Higher voltage versions tend to do better.

Yeah, filters essentially store power during one part of the cycle and release it during another. Net power lost is fairly minimal, though not zero. DC needs filtering too: all those switchmode power supplies are very choppy.

I’m not sure there are any power grids past the tens-of-megawatt range that aren’t just a 2/3/4 terminal HVDC link.

Railway DC supplies usually just have fat rectifiers and transformers from the AC mains to supply fault current/clearing and stability.

Ships are where I would expect to start seeing them arrive, or aircraft.

Almost all land-based standalone DC networks (again, not few-terminal HVDC links) are heavily battery backed and run at battery voltage - that’s not practical once you leave one property.

I’m sure there are some pretty detailed reports and simulations, though. A reduction in cost of multi-kV converters and DC circuit breakers is essential.

Ah, it’s been a while since I used ChromeOS. Looks like Flatpak was founded about the time I stopped.

Ah, it’s been a while since I stopped using ChromeOS. That’s an improvement.

PV inverters often have around 1-2% losses. This is not very significant. You also need to convert the voltage anyway because PV output voltage varies with light level.

Buck/boost converters work by converting the DC current to (messy) AC, then back to DC. If you want an isolating converter (necessary for most applications for safety reasons) that converter needs to handle the full power. If it’s non isolating, then it’s proportional to the voltage step.

Frequency provides a somewhat convenient method for all parties to know whether the grid is over- or under- supplied on a sub-second basis. Operating solely on voltage is more prone to oscillation and requires compensation for voltage drop, plus the information is typically lost at buck/boost sites. A DC grid would likely require much more robust and faster real-time comms.

The AC grid relies on significant (>10x overcurrent) short-term (<5s) overload capability. Inrush and motor starting requires small/short overloads (though still significant). Faults are detected and cleared primarily through the excess current drawn. Fuses/breakers in series will all see the same current from the same fault, but we want only the device closest to the fault to operate to minimise disruption. That’s achieved (called discrimination, coordination, or selectivity) by having each device take progressively more time to trip on a fault of a given size, and progressively higher fault current so that the devices upstream still rapidly detect a fault.

RCDs/GFCIs don’t coordinate well because there isn’t enough room between the smallest fault required to be detected and the maximum disconnection time to fit increasingly less sensitive devices.

Generators are perfectly able to provide this extra fault current through short term temperature rise and inertia. Inverters cannot provide 5-fold overcurrent without being significantly oversized. We even install synchronous condensers (a generator without any actual energy source) in areas far from actual generators to provide local inertia.

AC arcs inherently self-extinguish in most cases. DC arcs do not.

This means that breakers and expulsion type fuses have to be significantly, significantly larger and more expensive. It also means more protection is needed against arcs caused by poor connection, cable clashes, and insulation damage.

Solid state breakers alleviate this somewhat, but it’s going to take 20+ years to improve cost, size, and power loss to acceptable levels.

I expect that any ‘next generation’ system is likely to demand a step increase in safety, not merely matching the existing performance. I suspect that’s going to require a 100% coverage fibre comms network parallel to the power conductors, and in accessible areas possibly fully screened cable and isolated supply.

EVs and PV arrays get away with DC networks because they’re willing to shut down the whole system in the event of a fault. You don’t want a whole neighborhood to go dark because your neighbour’s cat gnawed on a laptop charger.

That’s not really practical. For a lot of on-call roles, you need the experience of working on the equipment daily to know how to fix it.

Even if you alternated e.g. a week of on-call then a week of normal shifts, you end up reducing the amount of time you have that is completely non-work.

Firemen are absolutely not doing nothing until called out. There’s training, maintenance, cleaning, post-incident paperwork, and probably other duties.

Most Fediverse stuff has web front ends so that any modern browser will work.

My concern would be that Chrome is about to neuter ad blockers, and you can’t use a different browser without replacing the OS.

Both are also heavily privacy destroying.

The issue is acronyms; there’s millions of products, schematics, datasheets, and manuals that refer to them as MISO and MOSI with no further explanation. Any new standard that doesn’t fit runs into the 15-competing-standards problem, and ought to be followed by an “AKA MISO” every time it’s used.

There should be no need for tuning, tweaking, or optimizing on functionality this basic.

If you ask the processor, it will spit out a graph like this telling you what threads/cores share resources, all the way up to (on large or server platforms) some RAM or PCIe slots being closer to certain groups of cores.