Playing the devils advocate, there's a slightly more nuanced aspect to
the "Apple tax" issue though, than just the one-time purchase.
According to Joe [http://goo.gl/SN0lD], RAM is 3x as expensive than
retail. And getting an SSD is also about twice as expensive as retail
(on top of that, OSX doesn't even support TRIM [http://goo.gl/asm9g]).
So taken into long-term context, it's hardly a slight issue for any
company with more than a few dozen developers craving new Mac hardware
every time Steve rolls up his sleeves.... ehh turtleneck.

On Nov 8, 3:18 pm, Kevin Wright <[email protected]> wrote:
> > And really, the only thing companies should be worried about when
> > getting hardware for there developers is: what's the hardware these
> > developers want? Getting slightly lower prized hardware, causing your
> > best developers to walk away is just irrational. I am just saying: for
> > software development companies, there *is* a business reason: allowing
> > your people with the tools they like will buy you a kind of commitment
> > that is priceless.
>
> +1
>
> Yes, I'm often surprised at how nit-picky some companies get about the cost
> of computers. Especially when you calculate:
>
> a) The cost difference of equipment as measured in man-days when compared to
> a developer's salary.
>
> b) The number of man days lost to the obligatory Windows anti-virus
> (especially expensive for activities that touch a lot of files - like
> compiling source code) and to idiosyncrasies of the Windows' command line;
> it can't take that long to recoup the extra cost of a Mac just by being able
> to use cmd+c / cmd+v.
>
> --
> Kevin Wright
>
> mail / gtalk / msn : [email protected]
> pulse / skype: kev.lee.wright
> twitter: @thecoda

-- 
You received this message because you are subscribed to the Google Groups "The 
Java Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/javaposse?hl=en.

Reply via email to