Live data from Hacker News

Smug Ugly, OSX presenting SMB shares

dashes.com

1–10 of 30 posts

Re: Smug Ugly, OSX presenting SMB shares

#2
It's an obnoxious image, and the author is right that Apple (and everyone else) should use either 10.5 or Leopard more consistently.

That said, I simply cannot remember the last time an Apple computer hard froze on me - not an application, the entire OS. It simply doesn't seem to happen. (Also his link to a picture of a crashed Apple (presumably?) seems broken.)

That said, I also run Debian, and complete system lock-ups never happen there either.

Re: Smug Ugly, OSX presenting SMB shares

#3

It's an obnoxious image, and the author is right that Apple (and everyone else) should use either 10.5 or Leopard more consistently. That said, I simply cannot remember the last time an Apple computer hard froze on me - not an application, the entire OS. It simply doesn't seem to happen. (Also his link to a picture of a crashed Apple (presumably?) seems broken.) That said, I also run Debian, and complete system lock-…

Windows doesn’t crash anymore. No more than OS X anyway. I do think, however, that the use of this icon is ok. It’s a cheap potshot at Windows but it’s only visible if you use Quicklook or Coverflow, no big deal. And, contrary to the author, I don’t believe that you should only mock if you are flawless.

(This is [2007], by the way. The BSOD icon is still there, though. It wasn’t removed with 10.6 update.)

Re: Smug Ugly, OSX presenting SMB shares

#4

It's an obnoxious image, and the author is right that Apple (and everyone else) should use either 10.5 or Leopard more consistently. That said, I simply cannot remember the last time an Apple computer hard froze on me - not an application, the entire OS. It simply doesn't seem to happen. (Also his link to a picture of a crashed Apple (presumably?) seems broken.) That said, I also run Debian, and complete system lock-…

I have hard lockups on OSX occasionally (1-2 a year) and it’s always down to badly written device drivers. Guess the same is true on Windows as well?

Re: Smug Ugly, OSX presenting SMB shares

#5

It's an obnoxious image, and the author is right that Apple (and everyone else) should use either 10.5 or Leopard more consistently. That said, I simply cannot remember the last time an Apple computer hard froze on me - not an application, the entire OS. It simply doesn't seem to happen. (Also his link to a picture of a crashed Apple (presumably?) seems broken.) That said, I also run Debian, and complete system lock-…

I simply cannot remember the last time an Apple computer hard froze on me

Whenever I have more than 100 browser tabs open, I get crashes at a rate of about one a week. Somehow, YouTube is always the straw that breaks the camel's back.

I love it. Keeps my desktop clean :-)

Re: Smug Ugly, OSX presenting SMB shares

#6
post #3

It's an obnoxious image, and the author is right that Apple (and everyone else) should use either 10.5 or Leopard more consistently. That said, I simply cannot remember the last time an Apple computer hard froze on me - not an application, the entire OS. It simply doesn't seem to happen. (Also his link to a picture of a crashed Apple (presumably?) seems broken.) That said, I also run Debian, and complete system lock-…

Windows doesn’t crash anymore. No more than OS X anyway. I do think, however, that the use of this icon is ok. It’s a cheap potshot at Windows but it’s only visible if you use Quicklook or Coverflow, no big deal. And, contrary to the author, I don’t believe that you should only mock if you are flawless. (This is [2007], by the way. The BSOD icon is still there, though. It wasn’t removed with 10.6 update.)

Actually, it can be seen in smaller version on the side of Finder under shared. I find it funny that i have two computer connected, one using NFS which shows up a cool LCD and another one using SMB showing up with the BSOD icon and both running Linux ;p

Re: Smug Ugly, OSX presenting SMB shares

#7

It's an obnoxious image, and the author is right that Apple (and everyone else) should use either 10.5 or Leopard more consistently. That said, I simply cannot remember the last time an Apple computer hard froze on me - not an application, the entire OS. It simply doesn't seem to happen. (Also his link to a picture of a crashed Apple (presumably?) seems broken.) That said, I also run Debian, and complete system lock-…

I simply cannot remember the last time an Apple computer hard froze on me Whenever I have more than 100 browser tabs open, I get crashes at a rate of about one a week. Somehow, YouTube is always the straw that breaks the camel's back. I love it. Keeps my desktop clean :-)

Yeah flash usually is the culprit for me too. It leaks ram

Re: Smug Ugly, OSX presenting SMB shares

#8

It's an obnoxious image, and the author is right that Apple (and everyone else) should use either 10.5 or Leopard more consistently. That said, I simply cannot remember the last time an Apple computer hard froze on me - not an application, the entire OS. It simply doesn't seem to happen. (Also his link to a picture of a crashed Apple (presumably?) seems broken.) That said, I also run Debian, and complete system lock-…

I've had it happen, and I also lost data on my MacBook. Apparently a disk was faulty. They say that can happen to anyone, but it never happened to me with non-Apple hardware.

Re: Smug Ugly, OSX presenting SMB shares

#9

It's an obnoxious image, and the author is right that Apple (and everyone else) should use either 10.5 or Leopard more consistently. That said, I simply cannot remember the last time an Apple computer hard froze on me - not an application, the entire OS. It simply doesn't seem to happen. (Also his link to a picture of a crashed Apple (presumably?) seems broken.) That said, I also run Debian, and complete system lock-…

I have hard lockups on OSX occasionally (1-2 a year) and it’s always down to badly written device drivers. Guess the same is true on Windows as well?

That's not always true - sometimes the kernel craps out if an application dies while trying to do something with the kernel (services especially). It doesn't make it Microsoft's "fault," it just means they should know that dumb situations like that are bound to happen.
Post reply on HN