The missing piece that makes it not a tautology is that two apps side by side have the same aspect ratio as one app full screen (but 90 degrees rotated)
Equivalence on what metrics? In theory what you are asking for makes sense, but I think it is very hard to actually specify what equivalent means in the context of an optimization process that needs to emit code with observably different behavior. Sometimes (although admittedly rarely) speeding up sections of code can even be undesirable for example branchless code for constant time algorithms that avoid timing or energy side channel leaks, or the much more mundane elimination of signed overflow checks or other undefined behavior quirks.
Listening to eskil’s talk from the better software conference, he said in order to stand on the shoulders of giants they must first stand still. I really like that metaphor, because it basically suggests today’s apps that have sprawling unaudited dependency graphs that change all the time is effectively teetering on the shoulders of stumbling giants. The visual seems very apt for the how brittle our current software industry feels.
I agree with that statement, but disagree with "The visual seems very apt for the how brittle our current software industry feels". It feels brittle, but for every single supply-chain-attack that has happened in the past year, nothing of significant was felt. So in the end, it seems like we're doing okayishly well.
I think you could make a case for that, especially when landing in water. Quite a few dense urban areas people might need to get to have water nearby suitable for landing seaplanes. I think you would end up creating communities further from the urban areas dedicated to this mode of transport. It’s definitely not a simple or guaranteed idea, but it is actually feasible politically and technically.
This! Anything unproven makes the flight certification process longer. They already have to get their electric side certified, might as well make the backup generator as easily certified as possible.
Regular aircraft are required to have enough fuel to be able to divert to the alternate airfield in their flight plan plus all the margins for taxiing and waiting for a landing clearance. If a plane is low on fuel they can declare an emergency and get priority over other traffic, but that obviously is disruptive and should not happen on well planned flights unless something pretty significant happens after takeoff.
You make it sound like it is acceptable for a badly planned flight to have a fuel emergency. It is not.
If there is a fuel emergency (or the plane lands with less than 30min of fuel) there will be an incident investigation that treats the situation as serious as if the plane had crashed. If the investigation discovers it was nothing more than bad planning, (at minimum) the planning procedures will be changed to ensure it never happens again.
> there will be an incident investigation that treats the situation as serious as if the plane had crashed
No the investigation isn’t as serious as if the plane had crashed. In July 2026 nine planes simultaneously had a fuel emergency in London. You bet it’s different from nine planes simultaneously crashing in London.
It helps to understand different kinds of fuel emergency. Declaring a fuel emergency to get to a diversion airport is very very different from having 30 minutes of fuel left.
Well, obviously it's going to be a much easier investigation, especially when you can interview all the crew.
But still very serious. 9 simultaneous fuel emergencies could have easily overwhelmed ATC and snowballed to worse issues.
Something lead 10 different aircraft to make the exact same mistake and find themselves without enough fuel for a safe diversion. There will be recommendations to try and prevent it from happening again.
Badly planned flights should not happen. Pilots who don't carefully plan their flights end up dead quickly. Lack of fuel is one of the easier to handle things that can go wrong from bad flight planning.
The pilots took exactly enough fuel to reach their destination. They didn't have enough fuel to divert to an alternative airport. They didn't even have the mandatory 30min of reserve fuel. They did not account for a minor holding pattern just before landing (ironically, because another plane had a fuel leak).
The crew failed to declare a fuel emergency, and crashed 18km from the airport. They had only been in the hold for 10 min when their engines ran out.. they were very short of fuel, the pilots knew they were short. They should have diverted (or declared a fuel emergency) almost an hour earlier, but they didn't want anyone to know how close they were cutting it.
My dad dreamed of being a pilot and when I was a kid he subscribed to the flying magazine (or something like that I don't remember that name.) every single issue had the last story being "I learned about flying from that" and nearly every single one was a case of bad planning, usually a case of flying into bad weather because of the bad planning.
I am struck by the fact that arguments for or against within this thread are only about perceived safety (something hard to know at a distance) and not the substance of the law involved. Does Virginia actually have laws prohibiting unsupervised 5 year olds? If so what is the minimum age at which children are allowed outside unsupervised? Does it also apply to leaving children at home unsupervised? The charge of “contributing to the delinquency of a minor” would suggest the minor’s behavior had to be illegal, which does not appear to have been discussed.
It is quite long, but I thought it was worth it if you can find the time. Short of that I think just reading the Knuth article the quote is from might bring similar insights.
I think the theory was that when each weight will be needed is predictable, so the latency can be hidden by fetching earlier (or more likely building the data in such a way that streaming it linearly brings the right weight at the right time)
I believe the comparison is with iOS not Linux. Android is Linux after all. It’s just that most programs don’t get to run a that level of abstraction, and instead run on top of a jvm. At least in iOS the code does seem to be able to be more efficient due to to higher usage of natively compiled code, which is what I think the op was complaining about.
There's no JVM in Android. Most important parts of an Android app are compiled ahead of time into CPU machine code, rarely used parts are compiled into machine code in runtime using JIT.
reply