|
Top-level
@PierreLebeaupin @chockenberry I was in the middle. I loved the Xserve, but it always seemed to have two time-limited purposes that had been fulfilled: 1) create a commodity-priced Datacenter server 2) show that Apple was an enterprise fit Both those things had been accomplished, and honestly, had everyone who was upset about the serve going away bought one? Probably have lasted longer. I liked them a lot, but I don’t recall being that upset about their end. It sucked, but it didn’t SUCK. 3 comments
@chockenberry @bynkii Well I seem to remember a MacWorld article implying a lot of profanity at the time… https://www.macworld.com/article/208838/xserve-30.html More seriously, I just tried to remember a past event that would have caused you, the local reference for profanity, a similar reaction to Craig’s; I’m not directly comparing the two announcements at all. @PierreLebeaupin @chockenberry oh holy shit, I forgot that article. Which brought back a lot of memories. I think I was really more pissed about the lack of communication (which apple is still just shit at) than anything else. I have no doubt the numbers supported the decision, but the lack of communication, and the absolutely obviousness that Apple did not have a good follow-up at the time were clear. Looking back, a lot of things are obvious, but at the time, ye gods. |
Gregory's Server
@bynkii @PierreLebeaupin @chockenberry I was a build engineer for products that ran on Mac and Win. We bought a LOT of Xserves (gritting our teeth about the cost premium vs our Win machines). Lovely machines!
I don’t know where we build our OSX products now - shortly after that I moved to a cloud product, where, because Apple didn’t allow virtualization, I never had to build on OSX again.
At the time it absolutely felt like a slap in the face to us as an enterprise customer.