> For many people, just having the function signatures is documentation enough.
You make a fair point about a documentation gap. The first step is always defining the problem. Wanting to add lots of realistic examples sounds like a wish for more tutorial or beginner-friendly content. Do you see the problem differently?
On the other hand, a given pure function type only has only so many possible implementations — why tools such as djinn and MagicHaskeller exist or why Hoogle is actually useful, unlike the horror of searching for every `void (*)(const char *)` in C.
From that perspective, Haskell docs tend to be more expert-friendly — perhaps a rationalization, granted — which seems ideally suited for an in-IDE model to help bridge between developer intent and typechecked code. However, this comes at the expense of putting in the reps to rewire the developer’s brain to think in functional terms and the resulting mind opening and horizon expansion to think new thoughts she wasn’t capable of even considering. In these days of LLMs, fretting over that particular opportunity cost may be thinking nostalgically about the loss of craftsmanship in fine, well-balanced buggy whips.
In the limit now, will all programming be strictly literate?
I understand that imposing the restrictions may have involved great amounts of wishful thinking as to the outcome. Even this is not so certain because certain politicians were able claim a victory for having Done Something by writing words on pieces of paper. It may even be against their interest — and they are self-interested actors despite claims to being detached public servants — to solve an issue that is evidently so effective at getting people so worked up.
Vendors’ compliance is not disputed, and you have produced no credible evidence of cheating. If there were demand for the smaller, more efficient engines that you’re fantasizing about, someone would already be building them with no legislative restrictions necessary. Under capitalism, any valid complaint can be rephrased as a business plan. You may not like how they complied with the law, but that’s a you problem. If you can’t bear to see it that way, then take it up with the inept authors of the restrictions. The purpose of a system is what it does.
Stating a broader principle in order to apply it to this instance, we in the U.S. are not obligated to go out of our way to pay more in taxes: “The legal right of a taxpayer to decrease the amount of what otherwise would be his taxes, or altogether avoid them, by means which the law permits, cannot be doubted” (Gregory v. Helvering, https://supreme.justia.com/cases/federal/us/293/465/). Similarly, the law requires manufacturers to meet the restrictions and does not require them to go out of their way to incur the enormous costs of design, certification, building and tooling up new factories, testing, hiring, training, etc., etc., etc. to produce entirely new engines. Anyone who seriously proposed such a rigamarole would have been accused of over-engineering or Rube Goldberging. Executives who put such a plan in place would have been sued and likely lost their jobs.
Intertemporal effects matter, but they are so frequently left out of what passes for economic analysis.
This is essentially the situation in the general aviation market for certificated aircraft, and it sucks. Costs are triple or more compared to the experimental market. Finding a decent mechanic is a serious chore. Repairs take forever.
1a. They may have thought they knew what they were doing, but their work product shows otherwise.
1b. They may have thought they knew what they were doing and spoke confidently enough to convince whoever was doing the acquisition, likely non-technical, of the same, but the bad hire and the bad hire’s work product shows that neither was the case.
2. Ideas merely exist. To be constraints, they must be enforced.
This is a surprising result. With structured inputs like source code, I’d expect grep to outperform semantic search, but natural language’s errors and inconsistencies seem to leave so many cracks for information to fall through.
Someone learning to fly may be described as paying careful attention: to every little sound, vibration, and sensation. A common tactic by student pilots is overcontrolling the aircraft, e.g., large sudden changes rather than smooth pressures from flying with a light touch.
Automation requires active, intentional attention particularly when flying in clouds. What are my instruments telling me? Are they all telling the same story? Have any failed? Which ones?
A significant part of flight training and testing emphasizes the ability to divide attention between multiple competing needs, being able to correctly prioritize them, and responding promptly and safely in order of priority.
The circumstance doesn’t have to be that dramatic to be abnormal.
Landing after a merely unstable approach, too many significant changes too close to landing, increases risk.
Landing too fast may result in overrunning the end of the runway, pilot induced oscillation, or loss of control. Energy being proportional to the square of velocity means the margin doesn’t have to be huge to pose significant danger. Landing too slow risks an aerodynamic stall or worse a spin, which at low altitude is nearly certain to be fatal.
Landing safely with a crosswind requires technique changes. Too much crosswind or “running out of rudder” is extremely dangerous.
Landing after accumulating airframe icing is triply bad because the ice reduces the control surfaces’ aerodynamic effectiveness, makes the airplane heavier, and requires a faster landing.
The FAA describes taxi, takeoff, landing, and operations other than cruise flight below 10,000 MSL as critical phases of flight because of increased risk. The aircraft is closer to the ground, other aircraft, and hazards such that prompt, correct responses are essential to the safe outcome of the flight.
Any equipment on the aircraft can and will fail. Becoming dependent on autoland — not a worry on most general aviation aircraft — is terrible risk management. Every pilot must maintain hand flying skills. Automation is nice and reduces workload, but the pilot must actively manage it.
This is an example of risk compensation. When people perceive greater protections around themselves, they tend to become more aggressive at the margin, such as with the driving habits that you mentioned or hitting more violently in American football because of improvements in helmets and padding.
> “It would not be an exaggeration to call these criminals capitalists,” he concludes, “even if their idea of making money was more literal-minded than the bankers whose notes they imitated.”
Counterfeiting is fraud, not capitalism. Even a so-called “lender of last resort” cannot exist under capitalism, but only under a system of dirigisme or worse.
Slowly lets you meet pen pals from your smartphone! Match with someone that shares your passions, write a letter, and collect stamps from around the world. Speak your mind—one letter at a time!
Letters take time to be delivered
The farther away your pen pal lives, the longer it will take to reach them. Why rush through replies? Make your letter be worth the wait!
Interesting concept, and I’m glad the magic was there for the two of you.
Words and ideas are meaningful. Finding a physical artifact from a far off place in the mailbox; seeing the stamps, markings, smudges, and other evidence of its journey; opening the envelope; and reading the other’s handwritten words add another dimension. Similarly, holding a paper book is a different experience, so I suspect that more than nostalgia is at work.