The Daily Parker

Politics, Weather, Photography, and the Dog

Whither the weekend?

I didn't even realize until just now I failed to post anything yesterday or today. I guess the weekend intervened. (Maybe the 18,000 steps I took yesterday had something to do with it.)

This coming week I'll be in all-day training from Tuesday to Friday, which may have some effect on posting. Or not, depending on how interesting the training is.

Autumn chill is upon us

While not the Polar Vortex of yore, it's definitely colder in Chicago now, even a little below normal. In any event, Wednesday and yesterday were the first two days that failed to get above freezing since March 4th and 5th, 253 days ago.

And it snowed yesterday. Again, not horribly unreasonable for mid-November, but not entirely common, either. But nothing so far suggests that our mild summer will be followed by a really cold winter; and in fact, the long-range forecasts are pretty normal.

Maybe we need a tuppence instead?

Damion Searls, writing for Paris Review, finds the link between language and the soon-to-be-extinct penny:

One thing we’ll lose, when the penny eventually goes the inevitable way of the half cent and the Canadian penny (extinct as of 2012), is the last possible link between our language of money and the everyday physical world.

A quarter is a fourth of a dollar, a dime a tenth (Old French dîme, Latin decima), a cent a hundredth or one percent—all math. Anyway, a cent is not a piece of money: a U.S. penny is technically a cent or one-cent coin, but in spoken language, a cent is a value and a penny is a coin. We offer someone our two cents, not two pennies; pennies can clink in your pocket, cents can’t. (When Americans adopted the British term penny in 1793, they took over the distinction, too: in England between pennies and pence.)

As for penny, its etymology is uncertain, though the ending implies a Germanic origin—the word used to be penning, with an -ing, like shilling and farthing, instead of a -y. The root may be Pfand, which turned into the English word pawn meaning “a pledge or token”: in that case, penny basically just means money. Or it may derive from the German Pfanne, “pan,” the round metal thing that you cook in. My head says it’s pawn: the pan pun sounds like classic folk etymology that somebody simply made up. But my heart belongs to Pfanne: surely the original coin goes back to some concrete reality, an object of actual use.

That said, the American penny isn't going anywhere. It's going to keep coming back like a bad...yeah.

Post-Schengen eerieness

The Atlantic's CityLab blog brings us the work of Ignacio Evangelista, who has photographed European border crossings abandoned after the Schengen treaty came into effect:

Evangelista has photographed many of these checkpoints over the last couple of years. Aptly titled "After Schengen," his project reinforces the suddenness with which many of Europe's border crossings went silent. Brightly colored vehicle gates remain at some boundaries, but they stand open, implying a warmer "Welcome," rather than "Stop!" (the latter can still be found on weathered signs and asphalt).

Despite the irrationality sometimes associated with national borders, the Schengen Treaty is as much an anomaly as it is an achievement. Many nations within the Schengen Area—Austria, Hungary, Poland, Czech Republic, Spain, France, and others—once represented a web of ambitious empires. The sudden abandonment of border crossings displayed in Evangelista's work, therefore, offers a reminder that Europe is in fact enjoying an historic era of peace.

I love borders. I have an idea for a coffee-table book, exploring borders and boundaries at various levels of abstractions, that I may just do someday.

One of these borders will surely be in the Baltics. The weirdest border checkpoint I saw was in Talinn, Estonia, at the ferry terminal. Finland and Estonia are both in the Schengen zone, but 25 years ago they were practically different civilizations.

Microsoft's impressive code drop

The Redmond giant stunned the software development world this week by opening up several core technologies, including the entire .NET platform, to the public:

We are building a .NET Core CLR for Windows, Mac and Linux and it will be both open source and it will be supported by Microsoft. It'll all happen at https://github.com/dotnet.

Much of the .NET Core Framework 4.6 and its Reference Source source is going on GitHub. It's being relicensed under the MIT license, so Mono (and you!) can use that source code in their .NET implementations.

Dr. Dobbs is impressed (as am I):

Of these platforms, Linux is clearly the most important. Today, Microsoft earns much of its (record) profits from enterprise software packages (SQL Server, SharePoint, Exchange, etc.). By running .NET on Linux, it now has the ability to run those apps on a significant majority of server platforms. Except for Solaris sites, all enterprises will be able to run the applications without having to add in the cost of Microsoft Server licenses.

But perhaps more important than the pure server benefit is the cloud aspect. VMs on the cloud, especially the public cloud, are principally Linux-based. Windows VMs are available, too, but at consistently higher pricing. With this move, .NET apps can now run anywhere on the cloud — or said another way, between servers and the cloud, the apps can run anywhere IT is operating.

The big winners of all this goodness are C# developers. In theory, .NET portability favors all .NET languages equally, but it's no secret that C# is the first among equals. (It is, in fact, the only language that Xamarin supports currently.) Microsoft has been an excellent steward of the language, evolving it intelligently and remarkably cleanly. Among developers who use it regularly, it is uniformly well liked, which distinguishes it from most of the other major development languages today, where an appreciation that borders on ambivalence is the more common experience.

The big loser is certainly Java. Java's stock in trade has been its longstanding ability to run without modification or recompilation on all major platforms. In this valuable trait, it has had no major competition. If Microsoft's port of .NET provides a multi-platform experience that is as smooth and seamless as Java, then the JVM will have some very serious competition.

Once I'm done with the deliverable that's due tomorrow, I may download the .NET Framework and take a look. I'll also spin up an Azure VM and play around with Visual Studio 2015 before the end of the week.

Another view of AF447

Journalist and private pilot William Langeweische writes in Vanity Fair last month that the Air France 447 crash may have more to do with automation than previously thought:

The problem is that beneath the surface simplicity of glass cockpits, and the ease of fly-by-wire control, the designs are in fact bewilderingly baroque—all the more so because most functions lie beyond view. Pilots can get confused to an extent they never would have in more basic airplanes. When I mentioned the inherent complexity to Delmar Fadden, a former chief of cockpit technology at Boeing, he emphatically denied that it posed a problem, as did the engineers I spoke to at Airbus. Airplane manufacturers cannot admit to serious issues with their machines, because of the liability involved, but I did not doubt their sincerity. Fadden did say that once capabilities are added to an aircraft system, particularly to the flight-management computer, because of certification requirements they become impossibly expensive to remove. And yes, if neither removed nor used, they lurk in the depths unseen. But that was as far as he would go.

Sarter has written extensively about “automation surprises,” often related to control modes that the pilot does not fully understand or that the airplane may have switched into autonomously, perhaps with an annunciation but without the pilot’s awareness. Such surprises certainly added to the confusion aboard Air France 447. One of the more common questions asked in cockpits today is “What’s it doing now?” Robert’s “We don’t understand anything!” was an extreme version of the same. Sarter said, “We now have this systemic problem with complexity, and it does not involve just one manufacturer. I could easily list 10 or more incidents from either manufacturer where the problem was related to automation and confusion. Complexity means you have a large number of subcomponents and they interact in sometimes unexpected ways. Pilots don’t know, because they haven’t experienced the fringe conditions that are built into the system. I was once in a room with five engineers who had been involved in building a particular airplane, and I started asking, ‘Well, how does this or that work?’ And they could not agree on the answers. So I was thinking, If these five engineers cannot agree, the poor pilot, if he ever encounters that particular situation . . . well, good luck.”

Airline pilot Patrick Smith, while acknowledging Langeweische's skills as a writer and his previously excellent reporting on aviation, calls B.S.:

I’m not arguing that pilots’ hands-on flying skill have probably become degraded over the years. But this is because a newer set of skills is required to master the job. A high level of competence is demanded in both skill sets, but it’s unfair, and wrong, to contend this newer set is somehow less important or less valuable than the other.

Neither is it anything easy to learn or master. The most frustrating take-away from the Vanity Fair story is that unless and until something goes wrong, flying modern planes is essentially effortless and without much challenge. The author’s point about the erosion of hands-on airmanship is a useful conversation. However, his contention that piloting jetliners is somehow easy, and his at-times cartoonish descriptions of what the job actually entails, is where the article falls apart (and pisses me off).

Professionals of all kinds will often describe a particular task as “easy.” What they mean, more correctly, is that it’s often routine; they are used to it. That’s not the same thing as easy. Try to imagine how much work — technologically, logistically, and so on — goes into getting a widebody jetliner with hundreds of people on it from one continent to another? It can be very routine, but nothing about it is easy.

Lawsuits are still ongoing.

Eight months since it was this cold

The first wintry cold front of the season has pushed through the Chicago area. Yesterday around this time we had a windy 16°C afternoon. Even as late as 6am the temperature still lingered around 12°C, not warm per se but pretty mild for November.

The cold front's leading edge hit around 7am and has now moved over the lake, leaving us with a chilly and gloomy 3°C evening and a forecast overnight wind chill below -10°C. Record cold temperatures are predicted next Monday and Tuesday.

Does this mean we're going to have another super-cold winter in Chicago? Probably not. Cold snaps happen; the Polar Vortex last year, that made the eastern U.S. the coldest spot in the world (relative to normal temperatures), was an extremely rare event.

Still, it might be time to break out the wool long johns...

Not many chances left

This is the airplane that took us from London to Chicago last Friday:

That's one of the remaining British Airways 747-400s, which they still use on some long-haul routes. They carry more cargo than A380s and B777s, which explains why they're still economical for BA to fly. But since Boeing no longer makes them, and since the B777 carries almost as much cargo with lower operating costs, BA is phasing the planes out.

My favorite plane in either BA's or American's fleets is the B767 that American still flies every morning from Chicago to London. American has made no secret of wanting to phase them out, too, but only a couple of weeks ago I found out they're going to phase in the B787s they've got on order. I can't wait—and I'm hoping they put the 787s on the same Chicago-to-London early-morning route that I love.