Yes. It takes us 5 seconds to an hour to actually come up with the fix, the remainder of the month is spent in bureaucratic hell - sitting in a trouble ticket queue, sitting in a verification queue, sitting in a QA manager's inbox, sitting with the communications team. Clearview, if it does what it says on the tin, only addresses the 5 second problem. Any "sane" dev shop would still run the resultant patch through the many cogs and loops of modern software management. You won't get your hole patched any quicker, you'll just have shifted the coders' attention away from your own app's bugs, and onto Clearview's bugs. Net gain: less than zero. Theoretically and conceptually, it's an interesting tool (you know, like Intercal). It just doesn't really fit in the industry, IMHO. [emphasis added]
You're missing the point. This isn't aimed at developers, it's aimed at end users.
It's kind of poetic how stupid you come off trying to dis on the global warming people.
1. Pretty much everyone agrees that the term global warming is bad, since what is happening is global climate change, which is very real and a very big problem.
I appreciate how you raised the level of dialogue with a carefully reasoned, logical argument backed up with facts.
I say stick to the status quo until we know we can't.
The problem with that is, what if the "oh we can't stick to the status quo" moment is actually a massive human extinction event? The risk is that the "bullet has already been fired" so to speak. It won't hit for another 50 to 100 years, but it's on the way, and it'll cause damage when it finally does hit.
And that's ultimate irony of the most hysterical proponents of human caused global warming. They believe that we're already irreversibly doomed and that no matter what economic devastation we wreak on the developing world (read: starvation exacerbation), all we will do is the equivalent of attaching a few life vests to the Titanic. So if we were to believe and heed them, what's the point?
*ducks*
No, you mean du -cks * |sort -rn |head -11:
Mobile: EU Commissioner Wants Standard For Mobile Phone Connectors
Ask Slashdot: Does Your Vendor Issue Gag Orders?
Your Rights Online: Pirate Bay P2P Trial Begins In Sweden
News: Spiraling Skyscraper Farms For a Future Manhattan
Linux: Microsoft and Red Hat Team Up On Virtualization
News: How Many Open Source Licenses Do You Need?
News: New York Wants To Tax Internet Downloads
Science: Earth Under Threat From Dark Comets
Technology: Nuclear Subs 'Collide In Ocean'
Your Rights Online: Facebook's New Terms of Service
So we have two basic options: pay for bigger hardware, or spend more time writing/maintaining custom code that allows us to live on our existing hardware.
Hardware is Cheap, Programmers are Expensive:
Given the rapid advance of Moore's Law, when does it make sense to throw hardware at a programming problem? As a general rule, I'd say almost always. Consider the average programmer salary here in the US. You probably have several of these programmer guys or gals on staff. I can't speak to how much your servers may cost, or how many of them you may need. Or, maybe you don't need any--perhaps all your code executes on your users' hardware, which is an entirely different scenario. Obviously, situations vary. But even the most rudimentary math will tell you that it'd take a massive hardware outlay to equal the yearly costs of even a modest five person programming team.
From someone who's a published author, I expect better grammar in a book review.
That's what editors are for. In real life, good writers may be horrible at proofreading their stuff, but be excellent at connecting with their audience and expressing things in an easy to understand and entertaining way. As one of my professors said in a writing class, "Grab your readers by the eyeballs!"
(Far be it from me to criticize your Grammar Nazi ways; I'm with you the whole way. I did, however, want to take issue with that one sentence.)
With your bare hands?!?