It's certainly not crazy to imagine that you could cut the costs of a helicopter-like aircraft that was purpose-made for relatively short, relatively low-speed, relatively light load duties.
The energy cost during operations is very relevant, too, which is why you see things like tilt rotor designs with wings/bodies to generate lift.
When Airbus was doing the math on these a few years ago, the pilot cost was also one of the main concerns, so it was "autonomous or bust", and they ended up investing a lot on the autonomous side (not just the aircraft but also urban traffic management, etc).
To clarify, it was an alignment of True, Magnetic, and Grid North. It was occurring at a point that happened to occur in England and was travelling slowly North for the past few years and now exists over water.
Magnetic North is the direction a compass points in a particular location and moves with shifts in earths magnetic field as well as local anomalies.
True North is parallel to the axis of Earths rotation and moves as earth wobbles and sways like a slightly unbalanced spinning top.
Grid North is perpendicular to lines of Longitude which is "fixed" to a given geographic reference frame. For the UK that would be OGSB36, GPS uses WGS84, other countries may adopt different systems.
All this means that an alignment of all 3 norths can occur at multiple places on earth or none at all.
I dont find the idea of a immutable "descriptive" tag or branch to be that useful (I also dont find the differentiation of tags and branches to be useful either) I've seen plenty of repositories where tags end up being pretty ambiguous compared to each other or where "release-20xx" does not actually point to the official 20xx release. Immutable references are more typically handled by builders and lockfiles to which Git already has a superior immutable reference system, the commit hash.
I 100% agree on the latter (the tag != release is more of a project management issue), and the same concept applies to containers and their digest hashes. The main issue at the end of the day is the human one: most people don't like looking at hashes, nor do they provide context of progression. I would say "give both" and make sure they match on the end user side of things, but tags are the most common way (open source) software releases are denoted.
> “Mr. Bojczak claimed that he installed and operated the jamming device in his company-supplied vehicle to block the GPS … system that his employer installed in the vehicle,” the FCC decision stated.
I'm not surprised that somebody would try and do this. However it is just so stupid at every level.
Well you start as the governor of the Bank of Canada for 5 years, then the governor of the Bank of England for another 7. After that you spend about 5 years in private finance. In parallel you spend that time acting as an economic advisor to multiple governments. Then the day comes where a major party needs a new leader, all the existing senior leadership either doesnt want it or is some manner of "problematic" and anyways, its not like they're going to win. Then whaddaya know, turns out Canadians like the idea of someone whose spent their whole life in macroeconomics at a time when global economics are all kinds of fucked up.
So it wasn't overnight, but it was a case of just the right person at just the right time.
Printed document isn't what I was on about. There the default should 100% be about accessibility (and then we just want that by default cause we're used to it).
PDF -> Nope.
.doc(x) -> Sure.
Website, OS, apps (including terminal) -> Sure.
Now regarding PDF I might've tried a long time ago when reading some old document (like CIA about MKULTRA). I don't remember if I succeeded. But there are PDF editors out there. I do think it likely screws layout (esp. larger documents), but that can be true for .doc(x) as well.
I think it would be a smaller issue if it only applied to digital media. Presumably though this applies to all media.
And I can certainly confirm that changing the font of PDF will almost always result in a unreadable mess. Something about how a PDF doesn't have text "blocks" and instead fixes each character making text reflow almost impossible.
"Winter" in AI (or cryptocurrency, or any at all) ecosystems denote a period of low activity, and a focus on fundamentals instead of driven by hype.
What we're seeing now is something more like the peak of summer. If it ends up being a bubble, and it burtst, some months after that will be "AI Winter" as investors won't want to continue chucking money at problems anymore, and it'll go back to "in the background research" again, as it was before.
Technically radiation cooling is 100% efficient. And remarkably effective, you can cool an inert object to the temperature of the CMBR (4K) without doing anything at all. However it is rather slow and works best if there's no nearby planets or stars.
Fun fact though, make your radiator hotter and you can dump just as much if not more energy then you would typically via convective cooling. At 1400C (just below the melting point of steel) you can shed 450kW of heat per square meter, all you need is a really fancy heat pump!
I dont have firm numbers for you since it would depend on environmental conditions. As an educated guess though, I would say a fucking shit ton. You wouldn't want to be anywhere near the damn thing.
A car's "radiator" doesn't actually lose heat by radiation though. It conducts heat to the air rushing through it. That's absolutely nothing like a radiator in a vacuum.
That's where the problem is.
reply