"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.

PHP is Turing complete, so it's technically possible to write anything in PHP that you could write in another language. That seems to be about the most it's got going for it. PHP does nothing to help programmers write sane, maintainable code. It's almost impossible to develop without having a browser tab open to php.net ("The online docs are great!" "Well, they'd have to be."). There is zero consistency with things like argument order. Dangerous legacy concepts like "mysql_real_escape_string" are only recently deprecated and don't have a set removal schedule. It's a one-trick pony that's nearly useless outside its niche as a web page generation language. It's just a mess - a dangerous, unmaintainable mess.

I won't refuse to use an app just because it's written in PHP, but I do heavily weight it when comparing alternatives. PHP is a powerhouse in much the same way as McDonald's. It may be ubiquitous, but it still sucks and you have to question the judgement of anyone who chooses it to start a new project.