artzy65, on 17 February 2013 - 06:23 PM, said:
WinTard, on 16 February 2013 - 09:11 PM, said:
don16140, on 16 February 2013 - 09:18 AM, said:
^^^
Here we go again! More FUD & BS from Microsoft haters and bashers.
Don't you know about the Internet Etiquette after 10 years? Geez! Some are sure slow learners...
No crashes you say? Hm.
It says otherwise right here:
Searching Bing for key sequence consistently crash OSX reveals:

What only 705,000 results?
Searching Google for key sequence consistently crash OSX reveals:

Ah, that's more like it, 45,100,000 results confirming this
Relax! And have a nice day!

Even bird heads can be happy and serene. Why all the angst? Everybody is cuter when happy!
PS: Do try that {hold down the shift key} and File:/// just for fun! Isn't it cool to be able to crash the entire OS X (the latest) with this simple 'magical-oh-wow-revolutionary' key combination?
Yet another Apple first! Aren't you curious? My good buddies in OS X assure me of the authenticity of this magical key sequence, which works on 99.99% in all applications under OS X.
PPS: Please explain the built-in antivirus in OS X?
~~~~~~~~~~
Never insult anyone by accident.
~ Robert A. Heinlein
Ignorance is trainable – Stupidity is terminal.
~ Jerry Fleming
Ignorance more frequently begets confidence than does knowledge.
~ Charles Darwin
Never underestimate the power of human stupidity.
~ Robert A. Heinlein
{Reformatted for clarity artzy65 post and working around the nested quotes limitations -WinTard}
You're picking on someone who isn't really tech-savvy. I don't know why you would waste your time like that. The 'uppercase' guy is relying on his own experience; he's pumped because he finds the change to OS X refreshing. One doesn't have to attack non-savvy users.
Aside from that, this is pretty interesting re that keyboarding issue http://osxdaily.com/...-apps-mac-os-x/



Is merely dispelling FUD with actual facts picking on someone? Did I state anything untrue? Did I start it? How would you go on about dispelling fallacies? And didn't you appreciate the subtle sarcasm?
I find it refreshing artzy65, that you can divine what others are really thinking about; based on such limited (and non-technical yet pumped) input? So this guy is just excited about OS X thus that entitles him (due to his lack of technical savvy) to bash Windows with malicious fallacies? Right.
As to the NO CRASHING part, well, I find it interesting that after all these years, one can bring down OS X (the latest in production, released in the field, not beta) with that simple key combination. Don't you?
Any computer crashing is a serious matter IMHO. Why? Because all unsaved works goes *POOF*! Whatever cached I/O buffers in the process of flushing in the background, *POOF*. Un-dismounted external drives, *POOF*. Worse even, if the HDD / SDD were in the process of writing at the instant of the crash, this potentially could under catastrophic conditions actually render the peripheral 'bricked'. Rare, but I've seen it happen. Traditional magnetic disks can usually be recovered from such failures, by a low-level formatting. Until fixed however, the device is completely invisible to the system. That is why Maxtor for example provide a MaxOrcize (MAXLLF) utility. The only significant drawback is losing precious data during this operation. Actually, I've found that SpinRite 6 from Gibson Research can non-destructively low-level reformat the damaged 'sectors' (since nowadays, drives do not use sectors anymore, but cram more bits on the outside circumference than the inner circumference section of the platters using zone-bit-recording and constant angular velocity -- but I digress.) If it were an SSD type, under catastrophic crash conditions, these could be rendered permanently damaged are currently unrecoverable from such incidents. 'Bricked". All data lost forever.
This clearly isn't an application bug, since it affects all the applications equally. This is an Operating System critical bug. Not merely a 'keyboarding issue' as you claim. In the article, they downplay the significance of this nasty OS X bug. They warn you to make a copy of the app, to avoid the 'infinite loop' which is a mere euphemism for OS X crashing. Friends have told me that even after the debug dump screen, the entire OS is dead, unresponsive, and must be rebooted. You can click anywhere, but OS X is dead.
Yeah, under lab conditions, one can control this crash, but most Apple users are confident that MacOS just works. Ironic eh?
Since this thread is about Crash-Proof computing, I thought this would be appropriate here?
As to the NO NEED FOR ANTIVIRUS, I'm still awaiting an answer to my question regarding "Please explain the built-in antivirus in OS X"? (This was a rhetorical question BTW).
So, what should I do? Simply remain silent in the face of blatant lies & fallacies? Is that what you suggest WinTarded people like me should do?
Unfortunately, I cannot see into people's minds, thus assume like you do, they were just excited and pumped up about OS X. And even if this were the case, a non tech savvy person (or anybody for that matter), doesn't need to trash other people's achievements in such a low class fashion spewing vitriol and fallacies. My stated mission is to debunk FUD (and not just here on PC World). I will do so every time I encounter it. Like it or not.
~~~~~~~~~~~~~~
To err is human. To moo is bovine.
~ God
This world is comedy to those that think, a tragedy to those that feel.
~ Horace Walpole
Our lives begin to end the day we become silent about things that matter.
~ Martin Luther King Jr., 1929-1968
The Zen of Python (not Monty-Python)
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than right now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
—Tim Peters
(This classic is also available in the Python interactive interpreter, just import this!)
Help





























