3 ms·

You're kind of robbing that phrase of its context by omitting the 'deploy to linux' part. I have nothing against windows devs developing on windows - in fact, I

You're kind of robbing that phrase of its context by omitting the 'deploy to linux' part. I have nothing against windows devs developing on windows - in fact, I can't offhand recall having met anyone developing desktop Windows software in anything other than Visual Studio - but when you're deploying to Linux, it makes an awful lot of sense to be developing on the same platform. Otherwise you're just begging for issues with dependency management, platform-dependent tests failing (you ARE running a test suite before committing, right?), even simple things like \n vs \r\n. It's useless trying to figure out why they're developing on Windows without having talked to them, but I for one can't come up with a good reason that doesn't warrant at least mild condemnation.

technomancy 16y ago
> but when you're deploying to Linux, it makes an awful lot of sense to be developing on the same platform. True, but he goes on to say the company he accepted deploys to Linux but develops on Macs. Huh?
- ahlatimer 16y ago
  Yes, but the number of potential bugs when going from OS X -> Linux are far fewer than going from Windows -> Linux.
  - deleted 16y ago
    [deleted]
- billybob 16y ago
  That's what we do. It works great for us.
  - technomancy 16y ago
    It's just a matter of time before a version mismatch or something bites you. My money's on the idiocy of the case-insensitive filesystem.
    - billybob 16y ago
      On our Ubuntu server, I can create both foo.txt and Foo.txt in a folder. On my OSX machine, those are considered the same file. Three reasons that's no big deal: 1) We never create both foo.txt and Foo.txt. Why would we? (OK, that's a bit snarky.) :) 2) We're developing on the system that's more restrictive (doesn't allow caps and non-caps versions) and pushing to the one that's more permissive. So nothing will get lost in the process. If we were going the other way, or migrating from Linux machines, I could see it being a problem. 3) If this is really a big deal to someone, they can configure OSX to use a case-sensitive file system. May cause other side effects (some Mac backup utilities may ignore either Foo.txt or foo.txt when backing up), but it can be done.

technomancy 16y ago

> but when you're deploying to Linux, it makes an awful lot of sense to be developing on the same platform. True, but he goes on to say the company he accepted deploys to Linux but develops on Macs. Huh?

ahlatimer 16y ago
Yes, but the number of potential bugs when going from OS X -> Linux are far fewer than going from Windows -> Linux.
- deleted 16y ago
  [deleted]
billybob 16y ago
That's what we do. It works great for us.
- technomancy 16y ago
  It's just a matter of time before a version mismatch or something bites you. My money's on the idiocy of the case-insensitive filesystem.
  - billybob 16y ago
    On our Ubuntu server, I can create both foo.txt and Foo.txt in a folder. On my OSX machine, those are considered the same file. Three reasons that's no big deal: 1) We never create both foo.txt and Foo.txt. Why would we? (OK, that's a bit snarky.) :) 2) We're developing on the system that's more restrictive (doesn't allow caps and non-caps versions) and pushing to the one that's more permissive. So nothing will get lost in the process. If we were going the other way, or migrating from Linux machines, I could see it being a problem. 3) If this is really a big deal to someone, they can configure OSX to use a case-sensitive file system. May cause other side effects (some Mac backup utilities may ignore either Foo.txt or foo.txt when backing up), but it can be done.