> At least with DevOps, there is no doubt that it's about Linux systems and automation.
Is that what you understand by the term "Devops" ? That "it's about Linux systems" ? Really??
That definition is a new one on me, and you very much should doubt it since "it's about Linux systems" is neither necessary nor sufficient. The confusion is even worse than I thought.
Are you trying a joke on Linux vs Unix? in reference to companies using Solaris or FreeBSD maybe? (there aren't many left of those).
All the DevOps roles I've ever seen are Unix based. In my experience sysadmin roles were more likely to be a windows administration or a helpdesk role than that.
I think it's pretty good devops got split into a distinct title. It's not a great experience walking into a sysadmin interview only to find out they are looking for an exchange administrator.
No, I'm saying the the DevOps ideas have nothing to do with OS choice. You could use them in linux or Windows or in any other OS; or you could ignore them in linux or Windows or any other OS.
> At least with DevOps, there is no doubt that it's about Linux systems and automation.
Windows Server still exists and maintains some market share. Automated, continuous delivery, and monitoring of web applications to Windows Server machines is DevOps in the exact same sense that it is with Linux machines.
The essence of DevOps is that there's no fence. The same team that writes the code deploys and monitors it. This essence remains unchanged regardless of the hosting platform - Linux, Windows, or even proprietary platforms like AWS lambda.
The most common name used to be sysadmin. That could be development or operations or anything down to running a Windows Active Directory or HelpDesk.
At least with DevOps, there is no doubt that it's about Linux systems and automation.