From my experience of doing software development professionally in several flavors of UNIX and Windows systems, I would say Linux is no better as there is seldom a way that works flawlessly across distributions.
I can't remember the last time I struggled building something on a random distribution that worked on another. What are you doing that you run into incompatibilities across modern Linux distributions?
It's certainly better than: "use VS" or "suffer through any other sort of Windows dev" in my opinion.
I'm constantly running into incompatibilities with my own code, all of them due to Debian. The one that's still causing me trouble is being able to invoke a pyuic4 that has access to both pykde and pyqwt; as far as I can tell that's impossible on Debian.
The third is the only that's tangentially related to the development pains we're discussing here. Packaging is a "fun" issue, but it's apples and oranges with multiple compatibility layers to get to a common denominator to be able to ... build a DCPU toolchain for example.
>Regarding your comment, there are many other ways to develop software for Windows besides VS.
Uh huh, and as seen even... right here... it's normally a (relatively) major pain in the ass to orchestrate.
Comments
Having "spent the effort" over and over again, I fully understand why hobbyists don't bother:
The Proper Way on Windows is a largely undocumented minefield strewn with broken glass and lack of a sane package managing system.
Personally, I require payment to even bother.
From my experience of doing software development professionally in several flavors of UNIX and Windows systems, I would say Linux is no better as there is seldom a way that works flawlessly across distributions.
I can't remember the last time I struggled building something on a random distribution that worked on another. What are you doing that you run into incompatibilities across modern Linux distributions?
It's certainly better than: "use VS" or "suffer through any other sort of Windows dev" in my opinion.
I'm constantly running into incompatibilities with my own code, all of them due to Debian. The one that's still causing me trouble is being able to invoke a pyuic4 that has access to both pykde and pyqwt; as far as I can tell that's impossible on Debian.
- Packaging
- Default installation directories
- so Dependencies
Regarding your comment, there are many other ways to develop software for Windows besides VS.
The third is the only that's tangentially related to the development pains we're discussing here. Packaging is a "fun" issue, but it's apples and oranges with multiple compatibility layers to get to a common denominator to be able to ... build a DCPU toolchain for example.
>Regarding your comment, there are many other ways to develop software for Windows besides VS.
Uh huh, and as seen even... right here... it's normally a (relatively) major pain in the ass to orchestrate.