brendn

The Concorde was an engineering marvel, but it was more than just increasingly cheap transatlantic fares that did it in. Noise regulations prevented it from flying over the Continental US. Maintenance became increasingly expensive as the fleet aged. (The technical problems with its air intakes and tires caused safety issues, too.)

It's easy to say it's an entirely economic issue, but it isn't. The 2000 crash of Air France Flight 4590 shattered passenger confidence, the post-bubble recession meant fewer people had the disposable income to buy tickets, and the post-9/11 slump in air travel further reduced ticket sales.

The article really only convincingly explains why we don't have a replacement Concorde, not why the Concorde went out of service. Jet fuel is expensive. Today, airlines and aircraft manufacturers spend trillions of dollars to improve fuel efficiency to keep up with rising fuel prices.

It's not that we're too cheap, it's that the the industry was more interested in advances in conventional jet efficiency so that airlines could reap the benefit across a much, much larger fleet.

There's always a desire to wrap up complex and multifaceted decisions in a neat little package. I don't think it's possible to point to a single issue (economic or otherwise) that made supersonic transport unviable.

By my understanding, yes and yes. The third-party service caches the public key (with timestamp) and the browser caches the signed certificate (with timestamp). The timestamp gives the credentials a relatively short TTL to prevent a stolen cert from being used indefinitely.

A friend of the author of QLB here, and I brought up the idea of a visual interpreter to parse the square kufic calligraphy. My understanding (limited as it is by my almost complete ignorance of Arabic) is that certain stackings of adjacent words would be ambiguous to the parser.

That's exactly what's happening in some places in Vermont. (I know, not the first place you think of when you hear 'solar.') People can buy shares of a solar co-op and get credited on their power bill for their portion of any electricity generated. It will be interesting to see how that model works in the long run.

Turing should be pardoned as a human victim of an unjust law, and his genius should have nothing to do with it. That said, there are more important fights for equality that affect living people right now than whether the British government officially pardons a dead man.

I'll have to try it out. Thanks!

I would love to see a LUA scripting framework built into this. I built an iOS app with an embedded web server, and dealing with dynamic text generation in Objective-C is a pain.

ConEd shut of power to the Financial District at approximately 7PM, but there were a number of explosions at substations including the one at 14th Street. There are over 1 million New Yorkers without power; ConEd reports most places below Midtown are dark.

They evacuated NYU Langone Hospital when its backup generator failed, so yes, consider yourself very lucky.

Most of Manhattan is without power. While some people may think it's badass to hack through the storm oblivious, the situation out here is pretty intense. I would encourage some leniency with the deadline, especially since as far as I know for NYC, things won't be back to normal for quite a few days.

I've heard (but can't find a link ATM) that it's not uncommon for people in developing countries have multiple phones or multiple SIM cards and will call on one or the other depending on that provider's current rates.

I'm curious about that issue, too. Here's a brainstorm:

- An independent Identity Provider (IdP) uses some means of identification for the user (two-factor, iris scan, whatever)

- The IdP provides an anonymized email address to each site that the user logs into.

I'll have to read the spec a bit more to see if that's possible...

I'd like to second this sentiment. Instead of tearing down someone's significant effort to build something cool, the community should constructively communicate their issues with the project and offer suggestions for improvement.

I was personally impressed that drag actions were supported, because that's a frequently overlooked aspect when people roll their own slider toggles. Without looking at the source, I would guess that implementing mobile touch events would go a long way towards making this library cross-browser.