waqf

Those aren't synonyms. A bell that is tolling is not pealing.

You're reading it correctly and it's working as intended. The people who should have reasonably expected that their job involves overtime are the ones who shouldn't be able to demand punitive extra pay when it turns out that their job involves overtime.

Maybe it sounds more palatable said the other way round: the people whose job can't reasonably be expected to involve overtime are the ones who most need statutory protection when they're suddenly asked to work overtime (because they didn't plan for it when negotiating their contract, for example).

Three roles — it gives individuals rights versus the federal government, which on the one hand is a fairly logical extension of a treaty between the states and the federal government but which on the other hand has the problems you describe — and it also gives individuals rights versus the states, which is a totally different and very weird kettle of ball games.

On the plain meaning of the text, an amendment like "Congress shall make no law …" wouldn't even bind the states in the first place, but apparently it does.

The other advantage of the UK system is that when the government comes up with some dumb new idea to abrogate human rights for people born on Tuesdays or whatever, the public debate is couched as "is this really a good idea?"

In the US it gets hung up on "is this constitutional?", which sort of misses an important point.

Most likely Mrs. Cringleton knew about the hyperbolic secant and just assumed it was unique up to linear factors.

> mom

> tea and bicuits

Where are you claiming to be from?

Well, most larger airports don't like you walking on the apron more than absolutely necessary, and if they don't have a jet bridge available they put you on a bus even if the plane is only a few yards away. But IIRC Frankfurt is the one where the bus actually goes out of the airport and down a public road?

Not technically routing instructions since each processor executed only from its own memory. To execute code on the other processor you'd have to do a block memory transfer over the Tube, then send a request to execute code at a stated address.

It doesn't, I was being ironic.

That's why I made an exception for widebodies, although I accept that "making an exception for widebodies" more or less undermines my point.

But I claim that, for example, you can't realistically have a 737 layout that isn't 6 seats wide in coach — and that means the width of your coach seats will be whatever width fits 6 seats plus one gangway.

To be fair, GP did address that point: the current renters of a city have votes [in local government], and the future renters do not.

But the seat width is determined by the seating configuration and the plane is designed so that one or two particular seating configurations will work well. (Although it matters less for widebodies where there's enough wiggle room to say "this plane will fit 8 reasonable economy seats or 9 ridiculously narrow ones".)

Direct flights to more destinations from any hub still means a superlinear increase in the number of slot pairs required. Are you suggesting that that wouldn't also be problematic at hubs in North America?

But New Orleans/London isn't two smaller cities, it's one smaller city and one major intercontinental hub. Doesn't expecting to have a nonstop flight from London to every city in the world put unsustainable pressure on landing slots in London?

Fix scrollback. Sometimes I run a command and it has 50,000 lines of output. Either I don't care about the output — in which case I should be able to click to fold it up and be able to see my history before that one command — or I do care about it, in which case I want every scroll, search and export operation that a full-fledged document editor would have.

In either case, UI latency shouldn't suffer, scroll bars shouldn't become unusable, my scrollback history before that one command shouldn't be thrown away — Mathematica notebook style, as another commentator suggests, might work well here.

Sure, but that's another way of saying the same thing. Because by "no realistic option" GP means, in effect, "no option that middle class people would stand for".

If you build a transportation infrastructure that's good enough for middle class people to rely on then middle class people will come to rely on it, and if you don't then they won't.

Well, that's silly too. They should play a separate pre-departure jingle 30 seconds or whatever before the train is expected to depart.

I don't see how you can justify the claim that a scrollable map with hotel locations and prices isn't "presented to actually help visitors".

Of course there's some synergy between helping visitors and profit to Google, that's how business models work. And if you think that following the links to hotels.com and tripadvisor.com will get you more altruistic and unbiased information than the Google links then I'd like to sell you this fine bridge with air conditioning, great views and swimming facilities, which 93% of visitors rated as 4 stars or higher.

And yet it sounds as if his restaurant wasn't totally nonviable, he just didn't have nearly enough runway for all his first-time mistakes. He might even be successful next time with what he's learnt, if he had the stomach for another go … and another $200k starting capital …

Isn't Southwest the one that just launched obligatory in-air concerts? https://www.economist.com/blogs/gulliver/2017/11/hitting-wro...

I think I'll give that a miss.

I have noticed that waiting around on the subway platform or at the bus stop is way more stressful than sitting on the subway or the bus, even if the subway/bus is just stuck for some incomprehensible reason and showing no sign of progress towards my destination.

This leads me to suspect that the stress of waiting for public transit is largely incidental and could be reduced by better station design, without having to make any (difficult, expensive) improvements to service frequency and reliability.

> Subways solve this problem by running every couple of minutes.

Similarly, in many transport corridors intercity rail runs several times an hour (not so much in the US) and shuttle flights run every hour or two. Which are also sufficient in those contexts, in that it becomes reasonable to show up at the station/airport without checking the timetable.

You begged the question here. The question is whether and to what extent the creator of software should have "ownership".

I think we should shift time zones a little every day, so that (in some designated location, say New York or DC) the sun rises at exactly 6am every morning. This eliminates the sudden transition to daylight savings which is the source of most complaints, and it would be trivial to implement with modern electronics.

There are two, somewhat overlapping, problems here which apply to a lot of parts of the entertainment industry.

The first is that supply exceeds demand: "everyone wants to be" an artist. This is basically unfixable.

The second is the very skewed distribution of revenue: a few big names get hundreds of millions of people's money, everyone else doesn't come close. This doesn't have to be that way at all (remember the 2000s when everyone was talking about the "long tail"?), but it would be a huge cultural shift and it involves a long discussion about commercialism and entrenched interests.

What's the point in the world having more art, culture and mythos if it doesn't have more that's accessible to any single individual? The best way for each new cultural artifact to reach the most people is for it to be created in a language and culture that the most people share.

AlphaGo is still based around layers of 3×3 local convolutions.

That represents a strong assumption about locality in the network design. I would expect AlphaGo to perform poorly on the game "Go with the vertices randomly permuted".

Only two states allow felons to vote while incarcerated: http://www.ncsl.org/research/elections-and-campaigns/felon-v...

I agree with the substance of what you say but I don't think it's wrong to invite everyone to have a general sense of the big picture.

And by big-picture standards, because of the way the US is constituted, the questions that make their way to SCOTUS are usually pretty strange.

So you could say that the algorithm for "should I claim any given intellectual property right?" is the one implemented by /bin/true.