Depends on what you are doing as a web developer. I work off Linux while the rest of my team is on OSX, but I'm also primarily a back-end developer and if I'm d

Depends on what you are doing as a web developer. I work off Linux while the rest of my team is on OSX, but I'm also primarily a back-end developer and if I'm dealing with HTML or CSS at all it's because someone else did markup and styling and handed it off to me to turn into a view. I don't really need to care about making sure everything lines up nicely across a bunch of different browsers or that the end result looks like whatever the graphic's designer promised the client. The front-end developers at my shop spend a lot of time interacting with the graphics department and less time interacting with the production servers, databases, etc. So they need to be on similar platform as the designers -- OSX. If they were on Linux the workflow of going between Adobe and Gimp would add an additional unnecessary hassle since frequently Gimp ends up rendering PSD files differently then how graphics is seeing it on their Mac. The downside is if they do end up being tasked with something back-end heavy they have to rely on virtualization or a development box running Linux. If, you're more involved in the back-end and spend more time interacting with the servers, building databases, models, writing deployment/automation scripts and not really touching the markup, then I figure it's best to be on whatever OS your production servers are running or at least something as close as possible. It just nice to have stuff intuitively work 1:1 instead of having to mentally remind yourself of the subtle differences between OSX and Linux or finding yourself relying on packages that are available on one OS but not the other. If I'm using Linux day in and out, I'm more likely to have a full understanding of how it works than if I'm only interacting with it in random encounters with the production and staging servers.