Landon Fuller has posted a gist on GitHub with an explanation of the bug and a binary patch to the affected library.
The most elegant solution to the calendar I've seen is JRR Tolkien's (yes, him) Shire Calendar:
- It's fully conformant with the astronomical realities (no magical even-divisions or date fudging necessary)
- There are still 12 months (so no weird decimal months, no 34th of Thermidor bollocks). You can stick with the familiar month names (rather than Tolkien's Hobbity ones)
- Each month is 30 days long (simplifying accounting, pay calculations, holiday accrual etc.). No pointless variation, no mnemonics.
- Year on year, a given month always begins with the same day of the week. Even for leap years. So if you were born on a Tuesday, your birthday will always be Tuesday.
- The clever part (which allows all the other stuff to happen) is there is a winter festival holiday (2 days) and a summer festival holiday (3 days normally, 4 in leap years). These aren't week days and aren't in a month - they're special. So e.g. Christmas doesn't change between sometimes being in the weekend, or adjacent to the weekend, or midweek - Christmas is always in the same place. I know I always get disoriented around Christmas - Christmas already seems like a special day which doesn't resemble a Thursday or a Sunday or whatever - the Shire Calendar is just a realistic expression that it's not a weekday, and that it shouldn't be regarded as one. And the first day back at work after Christmas is always a Monday.
- The winter and summer festivals are pretty consonant with common practice in many countries anyway. Move Christmas into the yule holiday (Jesus wasn't born in December anyway, so it's no less Biblically correct than current practice). Many countries have a midsummer festival or summer bank holiday and US independence day can be celebrated then.
- You only need one printed calendar (not the 14 different types we currently need) - you just score off the leap year or not.
- Its easy to fix the locations of other festivals, like Thanksgiving, and then you get a perfectly consistent gap between e.g. Thanksgiving and Christmas
- From a software perspective it's a wash - 2 more mini-months need to be handled, but less bother with differently lengthed months and much easier day-of-the-week calculations.
Technology companies are pretty good about properly integrating their marketing and public relations efforts into the business proper. So if they need to do a safety recall the PR people are involved in the process; a decent PR guy can turn "the XYZ-5000 sprays customers with burning acid" recall into "XYZ really cares about its customers, and as a lovely fluffy precaution we're fixing all our XYZ-5000s, even though most of them are perfectly super and don't experience moderate thermal variances". Engineering, QA, customer relations, finance - every department doesn't get to communicate with the public (or do anything that's obviously going to end up being public) without someone in PR there to make sure the message is put out right.
Legal departments, by dint of (often broken) corporate org-trees are a notable exception to this. When they see a problem, they fix it the lawyer way, and the rest of the company never knows until after the fact. In olden times of yore stuff like this was trivia between one legal office and another, and only the most nebbish of corporate historian ever know why a product changed its name or wasn't orange coloured any more. So the lawyers behaved as they always did, striking as quickly and as hard as they could, writing letters as outlandishly vitriolic and court pleadings as wildly exaggerated as they felt they could get away with, knowing that things would stay on the downlow and whatever happened only the outcome would matter to anyone.
They didn't consider that, if you sent someone a demand letter, the first thing they'd do is tweet about it to their entire customer base (which turns out to be a big proportion of your customer base too), and post the letter (with all its wild and crazy claims) on the internet, for everyone to point and laugh at. If it's the all-too-common shot across the bows (rather than a serious attempt) you risk looking like a rather unhinged bully.
Like it or not (and the lawyers don't like it, and decorate their broadsides with all kinds of "if you publish this letter we'll sue to for that too" stuff) everything anyone in the corporation does reflects on the whole outfit. The PR folks should be in on the ground floor with anything like this. They don't get to veto every lawsuit or every letter, but they can put a choke-hold on the stupid. Right now Zenimax's PR guy has his head in his hands; I'll bet the first thing he knew about the whole affair was when he read it online, and he'll spend next week fighting fires and soothing angry faces. Notch probably won't change the name, but if he does that's just another news cycle of bad PR for Zenimax.
They're not thinking about this for what we're currently call a "phone". They're looking at very small form factor devices which keep their data in the cloud, are configured by another (arbitrary) device which talks to the same cloud, and which make either sporadic or continual data connections with whatever available networks they find, to keep up to date. Imagine very small devices (wristwatches, eyeglasses, earplugs) with 802.11/UMTS/WiMAX radios (which use a mini-sim to identify themselves to whichever network they encounter). And they're thinking about these things as universal identifiers and payment tokens.
Right now you go running with an iPod. Instead you'll have a iPlug, a pair of little in-ear headphones, but with no cable and nothing strapped to your arm. You set up your music program on a tablet, and it seamlessly syncs. You run further than you'd expected, so the iPlug connects to the network and downloads more music. Miles from home your knee gives out. You touch the iPlug and say "taxi". A taxi comes (sent by Apple to the location the iPlug knew; Apple gets a dollar from the taxi fare, which you pay using the iPlug).
You have a iSim unit in your iWatch. You're thirsty, so you touch the watch and say "coffee shop". The watch face shows an arrow to a nearby one, and the distance, and walks you there. Apple gets a dollar. You buy a drink with the iSIM as a payment token (Apple gets 30 cents) and sit down at a table. The table's surface is an active display; it talks to your iWatch and opens a connection to your account in the iCloud. Your personal news appears, your emails, your documents. You do some work, browse some stuff, and when you're done you stand up and the table blinks off. Things will be as you left them when you next peer with an active display - at home, in the car, on the train, at the office, on the beach.
All of this stuff has been done, in various disconnected ways, already. You can pay for stuff with your phone, in some places. Most Europeans (well, Brits at least) have smart cards in their credit cards. You could hotdesk 10 years ago with a Sunray (kinda). You can unlock doors with a Dallas button token. Having super-cheap super-light totally ubiquitous networking makes the whole thing join up into a compelling, powerful, system.
You'll never be alone again.
I read the headline and assumed this would be another story about the TSA's screening procedures...
I hate to be the guy who complains about the headline of a story... but a "web bug" is an image in a web page or HTML email that allows the site owner to track who has visited the page or read the email. This story has absolutely nothing to do with "web bugs". How about "browser bug" instead?
Why would a corporation care about a grieving widow, unless there was some sort of bad publicity to arise out of... oh dear.
The better corporations realize that money isn't made from getting a customer, but maintaining good customer relationships with current customers. In this economy, no one can afford to provide poor customer service. I hope Verizon changes its policy to deal with the deaths of its current customers.
This will take science. It will take art. It will take innovation. It will take ambition.
It will also take the realization that the leading causes of death in the USA are all preventable:
- tobacco usage
- poor diet and physical inactivity
- alcohol consumption
There's only so much a doctor can do to stop the damage if the patient is already physically in poor health.
The political issue at hand is this: Should the government allow people to make irrational decisions when the mistakes can be costly or deadly? There is a movement called "soft paternalism" (http://en.wikipedia.org/wiki/Soft_paternalism) that basically argues that many people are making irrational decisions, so the government should gently nudge them into making rational ones. There are many books promoting this idea, including Nudge, The Paradox of Choice and Free Market Madness.
This sounds all nice and wonderful until you realize that it's ultimately politicians and bureaucrats that is deciding what is "rational" for a person to spend their money on -- like they're such great role models
I'll admit that my concept of our spending is probably skewed by intentionally misleading infographics and such, but this doesn't seem to jive with anything I've ever seen. Can someone explain how this is true, or point to something that does?
The cost of health care driving the US deficit and federal debt is actually old news:
http://www.iousa.com/ (30-minute version of the film film, highly engrossing)
http://www.pgpf.org/resources/PGPF_CitizensGuide_2009.pdf (Summary in PDF format)
I hate to interrupt a good old-fashioned witch-hunt, but AOL was instrumental in the creation of a little group called the Mozilla Foundation, transferring hardware and intellectual property to them and donating $2 million.
So maybe they're not all bad.
Link to Original Source