Not only that, but in many distros if you "upgrade" you can actually destroy base systems needed to manage the OS. Because upgrading Python is either painful or nearly impossible...
Point being that it is not unreasonable for companies to expect homogeneity and focus on innovating on features, rather than supporting dev environments.
In most cases, it isnt a problem, but often it turns out to be.
For example, my linux machine has vm.overcommit_memory set to 0, which Redis aint comfortable with.
What I notice, however, is that people dont mind when they are "forced" to work on OSX (and given free Macbooks). I wonder if it is truly standards "Nazi-ism" that people are concerned with or is it simply a case of teh shineeyy.
> Because upgrading Python is either painful or nearly impossible...
It's not actually that difficult. You need not upgrade your python. You just need one more python. I have been successfully using this setup on RHEL 5 and Ubuntu. And you can couple it with virtualenv and pip to have a sandbox. I would say it has become standard practice in the python dev community.
Not only that, but in many distros if you "upgrade" you can actually destroy base systems needed to manage the OS. Because upgrading Python is either painful or nearly impossible...
Point being that it is not unreasonable for companies to expect homogeneity and focus on innovating on features, rather than supporting dev environments.
In most cases, it isnt a problem, but often it turns out to be. For example, my linux machine has vm.overcommit_memory set to 0, which Redis aint comfortable with.
What I notice, however, is that people dont mind when they are "forced" to work on OSX (and given free Macbooks). I wonder if it is truly standards "Nazi-ism" that people are concerned with or is it simply a case of teh shineeyy.