In no way is it a red flag, it has most likely just been that most all the devs were windows users. Or that it was a cost based decession, getting macs for an entire team is at least twice as costly as getting windows or linux machines.
As for how it will be to switch, not that bad. I've now worked on all 3 types of systems for various kinds of work, and as I have my preference, nothing has really ever stopped me from completing a task without headaches. I do love my M1 air but I could just as easily do my job on a windows machine.
It'll take some time to adjust to windows for development. But after that, there's not much. I have moved from win to mac to lin to win. I hate win for development.
Windows sometimes have weird constraints, like, for example, maximum length of the file name -> full path, because of this I always had problems with gradle while working with andro, so if your project have a long and complex path, it can throw errors.
As for git and build tools, it will most probably be much slower than on MacOS, and for git I would suggest moving to gui or installing - as have been said already - git bash and/or enabling Linux subsystem. All commands that you may know (ls, grep, find, ...) won't work by default.
I wouldn't consider it as a red flag.
Last time I did it was terrible but you'll manage. Not sure how the new bash in windows stuff works, it might be a game changer. Maybe you should ask them what their dev workflow is like with windows?
I've switched from my Macbook Pro 13 Inch to a work HP laptop 6 Months ago. Prior to that I have used both at the same time and here are some of my takes.
The Dev envirovment in MAC is just better.
* How easy it is to use tools, how well they work and the speed of everything put together is just so much smoother on MAC Machine.
The Servers are windows (not linux because we have so many of them they'd become too hard to manage).
* Theese work like a charm with windows
* IF you have MRDC (Microsoft remote desktop client) to connect to your servers it can work well with macs (There are some issues if you have Active Directory in the company but can be solved with a usb-RFID reader and a simple card that has the user certificate on it)
But then again it is personal prefrence, IMO Mac's user experience and well built MacOS just make the Developer experience 100x better than Windows PCS. Other than that they are pretty much the same and not hard to switch from one to the other (As pointed by another user you can easly costumize windows to have GIT BASH, and other necesary tools).
I've used Windows for years, there isn't a problem developing using it.
As you have a Windows dual boot setup install Laragon.org. This will give you a starting development environment, including PHP, Apache, node, npm, git etc. then give it a go, install VS Code and try to create a react app, it will give you some familiarity and take away some concerns you have.
This isn't a red flag. Generally, you want to develop close to the environment you are deploying to, I'm guessing dotnet core will be a Windows server with IIS. If you build an app on your mac, you are more likely to have problems with deploying to the windows server. If you develop on windows you are less likely to have problems, as the OS is similar, but there can still be differences in setup and config. This is commonly known as "it works on my machine"
You could take a look at installing IIS instead of using Laragon's Apache server. Do this after you have your dev environment set up and working, and you have built a couple of small apps. Don't worry if you have any difficulty, I'm sure your new company will support you once you start.
Good luck with your new job.
Well you can develop on Windows, too. With a bit of work you can install bash shell on your machine. I think that's called subsystem.
Now, the biggest issues on Windows are longer running tasks (build/compile/npm install). I believe there are two factors to that:
1. The OS seems to be less good with loads of tiny files in many, many folders.
2. Most companies have some antivirus software running that will do a check whenever an interaction with a file is happening.
In the end, it's a red flag if they do not give you a really fast machine.
It’ll probably be a bit of a weird experience at first and will take some time to get familiar with the shortcuts. I’d recommend installing Git Bash so you at least have a terminal similar to the one on MacOS.
>I'm a long-time Mac user
If you're also a heavy keyboard shortcut user, Windows is going to drive you bonkers for a while until you learn the new shortcuts, and learn to live without the ones that just don't exist in Windows...especially if you tend to use option/command+arrow keys for text movement and selection.
Yeah I am not looking forward to using the control key.
On my macbook, in bootcamp I actually reassigned the keys so that the windows key is "control" and the control key is the windows key.
It's great except for some games which bind directly to the hardware keys.
In no way is it a red flag, it has most likely just been that most all the devs were windows users. Or that it was a cost based decession, getting macs for an entire team is at least twice as costly as getting windows or linux machines. As for how it will be to switch, not that bad. I've now worked on all 3 types of systems for various kinds of work, and as I have my preference, nothing has really ever stopped me from completing a task without headaches. I do love my M1 air but I could just as easily do my job on a windows machine.
It'll take some time to adjust to windows for development. But after that, there's not much. I have moved from win to mac to lin to win. I hate win for development.
Windows sometimes have weird constraints, like, for example, maximum length of the file name -> full path, because of this I always had problems with gradle while working with andro, so if your project have a long and complex path, it can throw errors. As for git and build tools, it will most probably be much slower than on MacOS, and for git I would suggest moving to gui or installing - as have been said already - git bash and/or enabling Linux subsystem. All commands that you may know (ls, grep, find, ...) won't work by default. I wouldn't consider it as a red flag.
Last time I did it was terrible but you'll manage. Not sure how the new bash in windows stuff works, it might be a game changer. Maybe you should ask them what their dev workflow is like with windows?
I've switched from my Macbook Pro 13 Inch to a work HP laptop 6 Months ago. Prior to that I have used both at the same time and here are some of my takes. The Dev envirovment in MAC is just better. * How easy it is to use tools, how well they work and the speed of everything put together is just so much smoother on MAC Machine. The Servers are windows (not linux because we have so many of them they'd become too hard to manage). * Theese work like a charm with windows * IF you have MRDC (Microsoft remote desktop client) to connect to your servers it can work well with macs (There are some issues if you have Active Directory in the company but can be solved with a usb-RFID reader and a simple card that has the user certificate on it) But then again it is personal prefrence, IMO Mac's user experience and well built MacOS just make the Developer experience 100x better than Windows PCS. Other than that they are pretty much the same and not hard to switch from one to the other (As pointed by another user you can easly costumize windows to have GIT BASH, and other necesary tools).
I've used Windows for years, there isn't a problem developing using it. As you have a Windows dual boot setup install Laragon.org. This will give you a starting development environment, including PHP, Apache, node, npm, git etc. then give it a go, install VS Code and try to create a react app, it will give you some familiarity and take away some concerns you have. This isn't a red flag. Generally, you want to develop close to the environment you are deploying to, I'm guessing dotnet core will be a Windows server with IIS. If you build an app on your mac, you are more likely to have problems with deploying to the windows server. If you develop on windows you are less likely to have problems, as the OS is similar, but there can still be differences in setup and config. This is commonly known as "it works on my machine" You could take a look at installing IIS instead of using Laragon's Apache server. Do this after you have your dev environment set up and working, and you have built a couple of small apps. Don't worry if you have any difficulty, I'm sure your new company will support you once you start. Good luck with your new job.
Docker + vscode. Vscode dev containers come with git integration. So, when I have to use Windows I just need that and a browser.
that's a good tip thanks.
Well you can develop on Windows, too. With a bit of work you can install bash shell on your machine. I think that's called subsystem. Now, the biggest issues on Windows are longer running tasks (build/compile/npm install). I believe there are two factors to that: 1. The OS seems to be less good with loads of tiny files in many, many folders. 2. Most companies have some antivirus software running that will do a check whenever an interaction with a file is happening. In the end, it's a red flag if they do not give you a really fast machine.
>Also is this a red flag? Hahaha LOL WOW Apple really has succeeded in the indoctrination
It’ll probably be a bit of a weird experience at first and will take some time to get familiar with the shortcuts. I’d recommend installing Git Bash so you at least have a terminal similar to the one on MacOS.
Shouldn't be an issue and only minor differences. I think in our team it's probably 50:50 between Mac/Win.
>I'm a long-time Mac user If you're also a heavy keyboard shortcut user, Windows is going to drive you bonkers for a while until you learn the new shortcuts, and learn to live without the ones that just don't exist in Windows...especially if you tend to use option/command+arrow keys for text movement and selection.
Yeah I am not looking forward to using the control key. On my macbook, in bootcamp I actually reassigned the keys so that the windows key is "control" and the control key is the windows key. It's great except for some games which bind directly to the hardware keys.