5 ms·

All of this is exactly why I love my Mac. Native unix capabilities with the ability to use the big names (Adobe, Microsoft Office, etc.). I have an RDP to a lap

All of this is exactly why I love my Mac. Native unix capabilities with the ability to use the big names (Adobe, Microsoft Office, etc.). I have an RDP to a laptop under my desk for anything Windows-related that needs a physical machine, but I live on my Mac.

Clubber 9y ago
I do the same but I also have VMWare Fusion for when I feel like doing Windows development. I created shortcut keys that match Xcode, so instead of [End], I use Cmd ->, etc. and they feel quite natural.
walshemj 9y ago
A Native to MAC unix environment almost all unix developers will be deploying to Linux so having a slightly different Unix is actually a risk, as is local development as opposed to a proper dev /test /prod set up
- cuckcuckspruce 9y ago
  Nonsense. You can have both - a local dev environment where you sandbox test your changes, a "proper" dev environment running Linux, a test environment running Linux that matches production, and a production environment. When you sandbox test your changes in your local dev you also quickly learn which pieces of your code are non-portable or non-standard.
  - walshemj 9y ago
    And your deploying on MAC hardware? Serious developments have identical hardware for dev and test to that used for prod. Its all about removing risk. I have worked at places were the dev test and prod systems where brought from the same sun production run so that the systems where identical down the rev of the motherboards, our networks and sysadmin said he would have liked to buy all the Disks (DASD) from the same production run as well.
    - cuckcuckspruce 9y ago
      Did you read my original comment which specifically mentions that development, test, and production are all matching? That you write and test the code before moving to the "proper" development environment running Linux gives you a chance to ensure you're not writing Linux-specific code in cases where portability at least a passing concern (read: unless you're developing platform specific firmware).

Clubber 9y ago

I do the same but I also have VMWare Fusion for when I feel like doing Windows development. I created shortcut keys that match Xcode, so instead of [End], I use Cmd ->, etc. and they feel quite natural.

walshemj 9y ago

A Native to MAC unix environment almost all unix developers will be deploying to Linux so having a slightly different Unix is actually a risk, as is local development as opposed to a proper dev /test /prod set up

cuckcuckspruce 9y ago
Nonsense. You can have both - a local dev environment where you sandbox test your changes, a "proper" dev environment running Linux, a test environment running Linux that matches production, and a production environment. When you sandbox test your changes in your local dev you also quickly learn which pieces of your code are non-portable or non-standard.
- walshemj 9y ago
  And your deploying on MAC hardware? Serious developments have identical hardware for dev and test to that used for prod. Its all about removing risk. I have worked at places were the dev test and prod systems where brought from the same sun production run so that the systems where identical down the rev of the motherboards, our networks and sysadmin said he would have liked to buy all the Disks (DASD) from the same production run as well.
  - cuckcuckspruce 9y ago
    Did you read my original comment which specifically mentions that development, test, and production are all matching? That you write and test the code before moving to the "proper" development environment running Linux gives you a chance to ensure you're not writing Linux-specific code in cases where portability at least a passing concern (read: unless you're developing platform specific firmware).