3 ms·
'I was just about to write a rant about how insane it is that windows people try so hard to run things that look "native" ' I don't think most Windows users ca
by nailer 17y ago
'I was just about to write a rant about how insane it is that windows people try so hard to run things that look "native" '
I don't think most Windows users care about looking native, it's more being native (and I don't understand why you put that word in quotes, Win32 / Unix are different APIs). Ie:
* Using Win32 services that your existing tool that monitors Win32 services works for (although you can hack this yourself for Cygwin).
* Logging to the event log, with all the existing filtering and remoting your other apps are using.
* Firing up a object shell with cmdlets for Windows administration rather than a regex-focused one focused on Unix commands.
* APIs available for languages you know, rather than ones you don't.
Imaging someone gave you a Windows app, to run via wine on Unix, that:
* lacked an initscript
* couldn't speak to syslog
* had documentation that assumed you were running powershell, not bash.
* Lacked a Python/Java/C API and provided a .net one instead.
and then ranted about how insane Unix people try so hard to run things that 'look native'.
PS - I'm a Unix guy. But for Windows, I'd use /n software Powershell server. It's a real SSH server for Windows, not someone's MSI wrapped around OpenSSH.
That said, if there was a real Win32 OpenSSH in the future, I'd probably switch to that.