Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

...what?

The 'cost', to Apple, of going to Enterprise is pretty large. Enterprises need things like stable patch schedules, forward-looking roadmaps, and integrated control structure. The toughest, culturally, on that list, is the forward-looking roadmaps. As one of many examples: Apple's switch from PPC chips to Intel chips was done with no warning & negatively impacted order fulfillment. (I was working at a university at the time, and lab computers ordered well in advance of the change were delayed 2 weeks -- other schools who ordered later were waiting months.)

Compare & contrast Microsoft's "patch Tuesday" with Apples "patch whenever". There's a cost to 'going enterprise' that goes far beyond "we don't want you to use this at work".

And that's not even touching the issue other's have pointed out regarding 'image' and 'branding' and emotional associations with the system you're using at the job you hate.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: