4 ms·

“traditional Windows devs are typically only good at Windows” — why? I developed for Windows, Nintendo, iOS, OSX… “NIX guys on the other hand are typically fam

“traditional Windows devs are typically only good at Windows” — why? I developed for Windows, Nintendo, iOS, OSX… “NIX guys on the other hand are typically familiar with multiple operating systems” Nope, they aren’t familiar with Windows. Just an example, I only see *nix developers started using I/O completion ports (which is the best I/O strategy for a Windows network servers since Windows NT 3.51) only couple of years ago, in node.js and libuv. Before that, most Windows ports of cross-platform servers failed miserably. “The typical, multi-threaded paradigms in C, Java, and C#” — for C#, those typical multi-threaded paradigm has changed in 2011-2012 with the release of TPL, Rx, async-await.

Mikeb85 11y ago
> Before that, most Windows ports of cross-platform servers failed miserably. No one cares about a Windows port of a cross-platform server because most will just deploy to a Linux or BSD server instance anyway... People only really care about Windows GUI apps...
- Const-me 11y ago
  “No one cares about a Windows port of a cross-platform server” — then who ported Node.js, Apache, MySQL, PostgreSQL, and the rest of them?
andyana 11y ago
I have to agree with the author: the Window's guy are usually the ones focused on Window's only solutions. Like, for example, a Windows admin having not heard of nmap. This is common.
- Const-me 11y ago
  Сould you please estimate what share of *nix admins have heard about VBScript, PowerShell, WMI or group policy?
  - andyana 11y ago
    I think you would find most unix admins know of those things. Powershell is your bash, WMI is your /proc. VBScript and group policy would be things you come across if you work with Samba.
    - Const-me 11y ago
      “Powershell is your bash” — Cmd.exe is your bash. Powershell doesn’t process text streams, it operates on .NET CLR objects. PowerShell by itself is more like interactive python shell. But it’s power isn’t language or interpreter, but the amount of things exposed to that language. “WMI is your /proc” — also ifconfig, /var/log, /etc/fstab, /etc/network/interfaces, and a lot more, and with remote access. “VBScript and group policy would be things you come across if you work with Samba” — completely unrelated. VBScript is more or less your Perl, but again with lots of things exposed to the language (besides WMI, there are ADSI, CDO, etc). AFAIK there’s nothing in *nix world resembling group policy. “most unix admins know of those things” — you see? Most unix admins know almost nothing of those things. So why do you expect a Windows admin should know about nmap? On Windows, people usually use other tools instead of nmap, e.g. netstat, portqry, and tcpview.
      - andyana 11y ago
        We can elaborate on those all day, but I nailed the gist of it and you know it.
        Const-me 11y ago
        No you haven't: powershell isn't bash, WMI is much more then a /proc, and both VBScript and group policy are completely unrelated to SMB/CIFS.
        andyana 11y ago
        VBScript would be something a Samba admin would know of due to VBS being used often for login scripts. Netlogon is a share you would have on your Samba server. Group policy is distributed over SMB. Is this news to you?
- matwood 11y ago
  I haven't used Windows in years, so I'm sure there are Windows oriented tools I haven't heard of.

Mikeb85 11y ago

> Before that, most Windows ports of cross-platform servers failed miserably. No one cares about a Windows port of a cross-platform server because most will just deploy to a Linux or BSD server instance anyway... People only really care about Windows GUI apps...

Const-me 11y ago
“No one cares about a Windows port of a cross-platform server” — then who ported Node.js, Apache, MySQL, PostgreSQL, and the rest of them?

andyana 11y ago

I have to agree with the author: the Window's guy are usually the ones focused on Window's only solutions. Like, for example, a Windows admin having not heard of nmap. This is common.

Const-me 11y ago
Сould you please estimate what share of *nix admins have heard about VBScript, PowerShell, WMI or group policy?
- andyana 11y ago
  I think you would find most unix admins know of those things. Powershell is your bash, WMI is your /proc. VBScript and group policy would be things you come across if you work with Samba.
  - Const-me 11y ago
    “Powershell is your bash” — Cmd.exe is your bash. Powershell doesn’t process text streams, it operates on .NET CLR objects. PowerShell by itself is more like interactive python shell. But it’s power isn’t language or interpreter, but the amount of things exposed to that language. “WMI is your /proc” — also ifconfig, /var/log, /etc/fstab, /etc/network/interfaces, and a lot more, and with remote access. “VBScript and group policy would be things you come across if you work with Samba” — completely unrelated. VBScript is more or less your Perl, but again with lots of things exposed to the language (besides WMI, there are ADSI, CDO, etc). AFAIK there’s nothing in *nix world resembling group policy. “most unix admins know of those things” — you see? Most unix admins know almost nothing of those things. So why do you expect a Windows admin should know about nmap? On Windows, people usually use other tools instead of nmap, e.g. netstat, portqry, and tcpview.
    - andyana 11y ago
      We can elaborate on those all day, but I nailed the gist of it and you know it.
      - Const-me 11y ago
        No you haven't: powershell isn't bash, WMI is much more then a /proc, and both VBScript and group policy are completely unrelated to SMB/CIFS.
      - andyana 11y ago
        VBScript would be something a Samba admin would know of due to VBS being used often for login scripts. Netlogon is a share you would have on your Samba server. Group policy is distributed over SMB. Is this news to you?
matwood 11y ago
I haven't used Windows in years, so I'm sure there are Windows oriented tools I haven't heard of.