You could call it a VW Type 1.
Posted on 02/21/2015 9:50:45 PM PST by Swordmaker
If cars crashed as often as computers... PC computers crash, Macs just run ...
The M$ car: giving new meaning to the Blue Screen of Death ...
Apple makes all of their stuff in China.
Except the Mac Pro and iMacs, as well as made to order imacs.
The free Linux car comes with a free ugly Administrator, just provide room and board ...
The iCar, affectionately known as the AppleCart, will be so reliably aware of traffic as to safely be able to cross any intersection without stopping. It will also know when the cops are monitoring the intersection . . .The iWatch automatically reminds its wearer not to sit in a chair for an hour without standing up and walking around; this based on the motto that “sitting is the new cancer.” The implication for car design is obvious; the AppleCart will be configured to safely allow the driver to transition from a seated to a standing position, and to get exercise, while the vehicle is in motion.
You heard it here first.
I was the biggest Apple detractor around, until my sister finally got me to come over to "the dark side". I was having my Dells crash a few times per year, and was replacing them every 2 years. I've had the MacBook pro for just under 6 years so far, and have not had it crash once.
I did have an ant get inside the screen once when I was using it outside, and the mouse trackpad had to be replaced when I spilled water on it... but that is the sum total of all of my problems with this laptop, and I have never once downloaded a single anti-virus program of any kind.
You can hate on the extra cost (which seems worth it to me after 6 years), and the weird Apple culture that some take to extremes, but you cannot accuse Macs of being crash-prone.
You could call it a VW Type 1.
I miss my Bug.
Did the computer crash, or did the iTunes and Safari software crash. I have never heard of either iTunes or Safari crashing the system. That would be very hard for either to crash OS X requiring a reboot. Usually if they crash, merely reload the program.
About 10-15% of iPhones are made in Brazil.
Want to play my computer is better. I have 18 Dells running WINDOWS XP 24/7/365 controlling my process network. Not one BSOD or hardware failure in 6 years and this is in a dirty. cutting fluid fumes and temperature hostile environment - not some office.
Are they connected to the Internet? And from what you say they are not used by people daily. . . pretty much dedicated machines doing the same things over and over. Right?
Ummm, Sword. Hang on a minute.
It is impossible to legitimately operate any Windows computer -- including Windows Server -- continuously for more than about 720 hours. Because Windows Updates every Patch Tuesday, and the virtually guaranteed need to reboot. Windows continuous operation is a joke.
OTOH, what the hell version of OS-X is she and are you running that hasn't required an update restart in seven years?
I daresay that, while the long run is impressive, it is hardly laudatory from a security point of view. What say?
I think if you'll go back and notice, I stated ". . .except for software updates" it has not crashed. . . and when we refer to updates, those are major updates. Minor updates often do not require system restarts. Third party software updates seldom require a system restart as they often do on Windows because software is not allowed to modify the system. On the other hand, we do have a server that has not had a system update in that entire time. . . it does not go on the internet—ever—and happily sits there running OS X.5 Leopard working as a back-up server with a RAID set-up. It's on a heavy duty UPS and has never even gone down in a power failure. Two drives have failed on it. . . but not the boot drive. Perhaps, one of these days, it will. I think it's been six to six and half years since we upgraded it to OS X.5.8 which would have been the last time it was rebooted.
Perhaps because of my long history with Unix, DEC VAX and RSX servers, and high-reliability industrial control systems, I still define "continuous operation" only in terms of "no interruptions of service", and I'm pretty hardline -- for example, restarting Apache to pick up a config file change can be done gracefully and inperceptibly, but it is an interruption of service if anyone's download gets stepped on.
A reboot is an interruption of service lasting typically a few minutes, between the start of service shutdowns and the time when all services are up again. But perhaps more importantly, a reboot reinitializes the system structures, clears caches, all sorts of refreshing cleanup occurs. The test of long-term system stability is whether it keeps going without that refreshment -- that proves there aren't any slow memory leaks, tables that don't have enough space and fill up, etc.
I know I'm being picky here, but my background taught me that counting "continuous operation" and ignoring reboots is just as, ummm, incorrect as counting "continuous fasting" and ignoring snacks. Fasting is fatal; anything less is not fasting, it's partial fasting. The reason RAIDs in HA systems are designed with hot-swap spares is exactly because in some systems any interruption is intolerable. For the smaller computers most of us work with, a reboot is actually a breather. :)
That said, I certainly acknowledge the validity of your description and achievement.
Like being a little bit pregnant. . . but we were discussing operating without crashing. . . and I was quite specific to include downtime due to updates.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.