Comment Re:$10,000 for handing in amateur astronomers (Score 1) 264
Any "amateur astronomer" who tries to do their laser-assisted star tour somewhere as light-polluted as the surroundings of a typical airport needs clue.
Any "amateur astronomer" who tries to do their laser-assisted star tour somewhere as light-polluted as the surroundings of a typical airport needs clue.
They've already got LLVM and Clang, no? Or did you mean better than those?
Just to be clear, "an Apple support person" did not say that. Nor would they. Ever. A tech calling Apple's engineering team clueless about anything? Surely you jest.
The original writer, Adam Pash, was clearly paraphrasing what the tech "explained" (his word) in his post at http://www.gizmodo.com.au/2014... - and even used bullet points to group the general themes, rather than quotes, to make it abundantly clear it wasn't a direct quote. The tech probably said something like "the engineering team isn't yet sure what the best course of action is," or something similarly honest-yet-noncommittal. Pash decided to simplify that as "clueless."
Selena Larson on ReadWriteWeb, for her part, changed "explained" to "told" (slight difference there, the latter being more direct, which this wasn't), and then our own redletterdave (or perhaps timothy) managed to change it to a direct quote. What is this, some twenty-first-century game of telephone? And we wonder why people still don't take online news seriously. Sigh.
I grew up in the Northeast Corridor (severely light-polluted), but for over 10 years have been on the "Big Island" of Hawaii and for almost 10 years, on Mauna Kea, so I'm used to 1-3 on the scale. Now I'm looking at moving back to be closer to family... hope I can find somewhere not TOO lit up.
That is a terrible policy. I spent a long night at an office of a fortune 500 company for that very reason. They didn't see any reason to apply bios patches because they were just to add support for newer hardware, not to fix any sort of vulnerability. Fair enough. Several years went by and their terminal server had a processor go finicky on them. They determined the available spares included processors that were compatible. I asked "has the bios been updated to support the newer processors?" I was assured that they do regular patching and it would not be a problem. I arrive on site, install the new processors and get no post. A bit of troubleshooting and we determine it doesn't recognize the processors because the bios was out of date. Really long story shortened - we had to shutdown another server, pull the processors, install them in the problem server, boot, patch the bios, shut down move the processors back in the donor server, and then reinstall the new processors. Of course this was in a server room that was an overstuffed shoe box so a number of acrobatics were required to get the servers extended to a point they could be worked on.
So what should have been a 10-15 minute processor replacement ended up causing several hours of downtime and the unscheduled shutdown of another server.
Don't be lazy!
That said, as someone else stated, I usually wait a couple months to patch (especially HP) unless it is considered a critical issue or I have a straightforward fail-over plan. HP has screwed my arrays etc. more than once with their quality updates.
"The only way I can lose this election is if I'm caught in bed with a dead girl or a live boy." -- Louisiana governor Edwin Edwards