3 ms·
Over eighty comments at this point, none mentioning developing on the same OS you deploy. Non-rhetorically, Is this no longer even a consideration?
by tejtm 4y ago
Over eighty comments at this point,
none mentioning developing on the same OS you deploy.
Non-rhetorically, Is this no longer even a consideration?
- smoldesu 4y agoThere are a lot of shops that bend over backwards for MacOS support. In the past, I've seen substantial internal teams get made just to ensure the product runs on MacOS. Mind you, MacOS was not a supported client target, it was just the OS everyone wanted to use for development. Logic like that just sends my mind reeling. I don't really know what software development looks like anymore, but sadly the build/deploy homogeneity is lost on a new generation of developers.
- tensor 4y agoIt's not lost, it's just not relevant. Build is generally done in CI/CD often on the same OS as arch as deploy. But even then, with the rise of languages that can trivially cross compile it's just not as important as it used to be.
- smoldesu 4y agoYou're right, at least in my experience. That being said, it's a sad sentiment that all of our development is moving off-machine to computers that could just as well be our local device.
- TillE 4y agoWhat's to consider? Obviously I write Windows software on Windows, there's no realistic alternative. For software that runs on all of Windows/Mac/Linux, I...still generally use Windows, because Visual Studio is really good for C++ and C#. I do like macOS for embedded development, though.
- tester756 4y agobut why? I develop C# on Windows and deploy on Linux without problems
- deleted 4y ago[deleted]