4 ms·

Not to diminish your point, but there are cases where running application development is very easy on a mac, and linux comes as first and subsequent stages of t

Not to diminish your point, but there are cases where running application development is very easy on a mac, and linux comes as first and subsequent stages of the CI pipeline. > working dev environment need to be done ONCE good point, I personally would rather integrate everything into the development platform (i.e. front end http server would be just another npm package/middleware, but not NGINX, everything gonna end up under a load balancer anyway on prod/test). In regard to different machines/OSes, issuing everyone a mac really takes away a lot of headache for organisation, at a relatively small (compared to engineering hours) cost.

stephenr 9y ago
> good point, I personally would rather integrate everything into the development platform The problem is, that restricts you to what's available for your dev platform. How many nodejs http servers do ESI sub requests, or can parse and use the same VCL file as Varnish uses on prod? > In regard to different machines/OSes, issuing everyone a mac really takes away a lot of headache for organisation, at a relatively small (compared to engineering hours) cost. I mean, there are benefits to standardising your work force, but I don't really see your argument here because: a) if you take this route, and then don't use Vagrant, you have to pay each and every one of your engineers to re-setup all their projects, whenever they need to re-clone them (failed hardware, wipe & install OS update, etc). b) unless you buy everyone the same new mac at the same time, you don't have the same environment, and it's doubtful you all even have the same OS version. c) I've never worked in a company where everyone was happy to use the same tools/platform for dev. Forcing people to use a platform they don't like, in favour of using an open source tool that solves the problem, sounds like making things harder than they need to be d) not all projects are run by a company, or even by the same company. Freelancers collaborating is a thing.

stephenr 9y ago

> good point, I personally would rather integrate everything into the development platform The problem is, that restricts you to what's available for your dev platform. How many nodejs http servers do ESI sub requests, or can parse and use the same VCL file as Varnish uses on prod? > In regard to different machines/OSes, issuing everyone a mac really takes away a lot of headache for organisation, at a relatively small (compared to engineering hours) cost. I mean, there are benefits to standardising your work force, but I don't really see your argument here because: a) if you take this route, and then don't use Vagrant, you have to pay each and every one of your engineers to re-setup all their projects, whenever they need to re-clone them (failed hardware, wipe & install OS update, etc). b) unless you buy everyone the same new mac at the same time, you don't have the same environment, and it's doubtful you all even have the same OS version. c) I've never worked in a company where everyone was happy to use the same tools/platform for dev. Forcing people to use a platform they don't like, in favour of using an open source tool that solves the problem, sounds like making things harder than they need to be d) not all projects are run by a company, or even by the same company. Freelancers collaborating is a thing.