4 ms·

- Powershell sucks - Graphical installers / no package manager - No search results / docs for most languages - Weird bugs due to being second class for most

- Powershell sucks - Graphical installers / no package manager - No search results / docs for most languages - Weird bugs due to being second class for most languages - Have to use docker in VM - Bad env for writing scripts - We deploy on Linux

Kipters 6y ago
Some of these are fixed or there's progress being made: - IMHO PowerShell is not that bad, but the newer PowerShell Core works better and with WSL you can use your favorite linux shell (and mix and match Windows and Linux binaries) - WinGet is in preview - No search results: my experience is 50/50 on that - second class citizen: I wouldn't say most, definitely for Golang - Docker now runs on WSL2 (which is still a sort of VM, but in my experience it's night and day with the old VM and especially compared to the default Docker experience on macOS) - Why? You can use Python, and scripts are where Powershell really shines as a language - That's the entire point of WSL I guess
- FridgeSeal 6y ago
  PowerShell is horrible and confusing to use. Maybe I’m just dumb, but it was confusing to learn and super unintuitive. If I’m running everything in WSL/2 why not just run Linux? I don’t remember the last time I had to use something windows specific - and word is available online for the sporadic times that needs to be used.
  - Kipters 6y ago
    What I've found to be most alien to people used to bash is that Powershell is fundamentally different because of its object-passing style instead of dealing with text streams, usually once someone gets a grasp on this their experience using powershell improves significantly About WSL, you're right: if you only use WSL it doesn't make sense to use Windows, but it's a good compromise for anyone who needs both at the same time (at least it's a better compromise than a VM)

4 ms·

- Powershell sucks - Graphical installers / no package manager - No search results / docs for most languages - Weird bugs due to being second class for most

by deleuze 6y ago

Kipters 6y ago
Some of these are fixed or there's progress being made: - IMHO PowerShell is not that bad, but the newer PowerShell Core works better and with WSL you can use your favorite linux shell (and mix and match Windows and Linux binaries) - WinGet is in preview - No search results: my experience is 50/50 on that - second class citizen: I wouldn't say most, definitely for Golang - Docker now runs on WSL2 (which is still a sort of VM, but in my experience it's night and day with the old VM and especially compared to the default Docker experience on macOS) - Why? You can use Python, and scripts are where Powershell really shines as a language - That's the entire point of WSL I guess
- FridgeSeal 6y ago
  PowerShell is horrible and confusing to use. Maybe I’m just dumb, but it was confusing to learn and super unintuitive. If I’m running everything in WSL/2 why not just run Linux? I don’t remember the last time I had to use something windows specific - and word is available online for the sporadic times that needs to be used.
  - Kipters 6y ago
    What I've found to be most alien to people used to bash is that Powershell is fundamentally different because of its object-passing style instead of dealing with text streams, usually once someone gets a grasp on this their experience using powershell improves significantly About WSL, you're right: if you only use WSL it doesn't make sense to use Windows, but it's a good compromise for anyone who needs both at the same time (at least it's a better compromise than a VM)