You seem to be under the impression that backward and forward hardware compatibility are easy things:

1) That an arbitrary OS could be expected to run well on hardware made many years in the past and many years in the future, and
2) That arbitrary hardware can easily support ancient software.

Suppose you'd said this about DOS. Microsoft should support it in perpetuity! OK, then, but where are you going to buy a mouse today that supports the hardware ports that DOS knows how to handle (or would you think mouse makers would spend the effort to write MTRACKPAD.SYS so that a new Apple Magic Trackpad would work on it)? And it's not exactly free or cheap for a modern i7 to maintain 100% 8088 compatibility.

Conversely, should iOS 9 be expected to run on an original iPhone, with CPUs and GPUs many times slower, an eighth the RAM, a fraction of the storage, and utterly obsolete in many other ways? Even if the minimal core could be made to run, so many features would have to be stripped out (at great development and testing expense) that it'd be pointless.

There are good reasons for dropping compatibility. Software isn't easily made to scale down to ancient predecessors, and hardware leaves stuff behind regularly - I don't have serial ports or ISA slots on this motherboard. It's not plausible for Apple to carry iOS all the way back to hardware that almost no one is using, and it's not realistic for Microsoft to drag Windows 7 all the way forward to hardware that hasn't even been conceived yet. At some point, you just have to let go.

"Swift" was a generic noun and a generic adjective long before Taylor's ancestors started using it. I've never seen a wild dylan or ran dylanly down a racetrack, though.

Apple did not do this unilaterally. They approached the rightsholders who actually own the music - that is, the labels and not the artists - and proposed this arrangement. After much negotiation, everyone agreed that this was a solid plan and started moving ahead with it. How much money Apple does or doesn't have is immaterial because they could not legally do this without the consent of the people who own the material, and those people thought it was a fine idea and signed on the dotted line.

So yes, it's perfectly fair: not because you or I think so but because the people capable of vetoing it said it is.

Did I misinterpret that, or did you really mean to say that £40,000/year is a plausible amount for an IBMer to make while living in London? What would you say is a nice salary for a senior engineer?

Don't underestimate the value of free entertainment. Sometimes that guy coming home from his second job really needs to unwind a little before he gets his 6 hours of sleep, and a little YouTube is probably a healthier and cheaper alternative to an after-work beer. Also, entertainment has traditionally proven useful to help prevent the proles from revolting against the bourgeoisie. It's generally not a great idea to insist that the poorest be made more and more miserable for their own good.

You shouldn't worry about it. From everything I've seen, he's a lot more sympathetic to new contributors making mistakes than he is to old-timers who should know better. It's fair and reasonable to hold them to a higher standard, and that seems to be exactly what he does.

It is at fault. It's the job of the wrapper to present a consistent interface to the things being wrapped. Otherwise, why even bother?

And yet the only PHP command line utilities I've ever seen are shells for controlling PHP web apps. I've never seen a PHP GUI app so I can't speak to that.

For being as allegedly suitable for developing those kinds of things, almost no one seems to be doing it.

Yes, it is. There are plenty of languages that can cleanly generate web pages and system and application development. Web frontends are important and popular, but hardly the end-all be-all of modern programming. PHP is losing a lot of ground to single-page frameworks like AngularJS. It never had ground for backend platform development outside a handful of visible companies: for every Facebook, there are 100 companies with Java or Python infrastructure platforms.

I contend that PHP is good at exactly one thing: gathering data from backing stores and formatting it as HTML. That's being quickly superseded by browser JavaScript or portable device apps that fetch the same data through REST and format it themselves.