Thanks for the advice. I guess there are three issues:
1. the risk of developing in an environment different than the production environment. I mitigate the environment risk by system testing on a test server identical to the production box prior to deployment. I imagine it would be pretty difficult to set up an identical environment on your own development box, since the hosting company always has their own unique system images which you don't have access to. 2. The scripting power of Linux to facilitate automating stuff in development Since cygwin/mintty provides a bash shell for windows which can run native linux scripts (again I am just starting with it so can't vouch for it's efficacy, but it is supposed to enable you to script just about anything you could have done on linux), I don't know if there is that big of a difference. 3. The personal productivity of a desktop os like Windows/Mac, and it's interoperability/document exchange capabilities with the rest of the non-development world If you're developing on windows/Mac, there is no issue here. 4. the inability to use all the functionality provided by Symfony2 to the fullest. eg. - Symfony2 shell (app/console -s) doesn't run on windows (not sure what it does, so don't know what I'm missing); - no php_posix on windows which symfony2 uses to color it's fonts. I don't know if there are any other things Symfony2 or Doctrine2 don't support on windows. -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" 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/symfony-users?hl=en
