But the screens should look different, right? That's the point of building separate iOS vs. Android versions is to make each version "native" to its platform. The feature-set should be the same, but the interfaces can diverge.
If you want to know what flying first-class 50 years ago was like (and you live in southern California, and you have money to burn) you can try the Panam Experience (https://panamexperience.com/). It's a replica of a Panam 747, together with a "crew" in period-correct costumes, that tries to recreate the entire experience of flying in the 1950s. (Bearing in mind that the plane is a replica, located on a soundstage.)
That sounds a bit weird, the 747 didn't enter commercial service until 1970.
A 1950s flight experience would have been on something with piston engines and propellors, like a DC-6 or a Super Constellation. Noisy, turbulent, and not particularly safe by modern standards.
I flew in piston airliners long ago. They fly low and slow, and barf bags are supplied for a reason (low altitude means lots of turbulence).
Today's airliners fly high where the air is smooth, they've gotten very good at avoiding turbulent weather, and there are automated damping systems. The barf bags are still there, but I've never seen anyone use one.
The cool thing about piston airliners, though, is the the engine start.
I have flown in turboprops, which start just like a jet engine. Yes I bet the startup of a big Pratt & Whitney Twin Wasp or Wright Cyclone, belching smoke and fire would have been something to see.
Today's high bypass jet engines also qualify as a turboprop.
The sound of a Merlin V12 coughing into life is just pure joy. My dad had the best job in the world flying P-51s (powered by Merlins). I hired a P-51 to do a flyby at his funeral. I only had to pay for the gas.
Ah, I responded to "tries to recreate the entire experience of flying in the 1950s" and not the "50 years ago" yes in the 1970s it could certainly have been a 747.
A proof is not like a program. The goal of a program is to "do the thing", thus you can make the argument that it doesn't matter what the code looks like as long as its works right. But the goal of a proof isn't to "do the thing" (where "the thing" is just to print Yes or No), it's to communicate. An unintelligible proof is really just a first draft.
I think the algorithm recommended Chris to me because of his topology videos, and from there I watched all his "old computing devices" stuff. Something about the Boston accent, the dry humor, and the occasional audio jump-cut make his stuff quite funny.
