4 ms·

I develop on Windows 10, and I don't try to "Linuxize" at all, even though we often deploy on Linux. I do use ConEmu, but I use PowerShell as my shell, don't r

I develop on Windows 10, and I don't try to "Linuxize" at all, even though we often deploy on Linux. I do use ConEmu, but I use PowerShell as my shell, don't run WSL or Cygwin. All our devtools (Erlang, CUDA C/C++, Python) run fine in Windows and using Windows as it was meant to be without any "shims" makes it much easier to deal with differences in file nameing conventions, path separators, etc. Plus, PowerShell really is the Best Shell Ever.

hungerstrike 9y ago
I too develop Node.js apps on Windows 10 and I'm with you - there is no reason to go out of my way to make it more Linux-like because everything just works. I use Cmd over PowerShell though since PowerShell can't process commands separated by "&&", which are used extensively in package.json scripts. I'm happy with this setup though since I don't think the CLI is a good interface at all (I prefer GUIs with lots of keyboard acceleration), so I tend to minimize CLI use as much as possible by automating everything down to single, simple commands. With VSCode, I can run my package scripts in the built-in terminal as well. Also, if I do have to edit some code on my Mac or Linux boxes (which I usually reserve for just compiling and testing things), VSCode gives me the same experience everywhere. I like that a lot!
pjmlp 9y ago
Me too, development is mostly done in .NET, Java and C++. Software that needs to be deployed on UNIX systems is usually written in Java. All the scripts that I need to access on both systems are written in Python. I rather make the best use of the tools each platform offers.
zaphar 9y ago
Powershell is an amazing shell scripting language. But it's a terrible daily driver of a shell. Everything is an enormously long line to type. Yes you can make aliases for common stuff but that's non-standard and not portable. The primary purpose of a shell is not scripting. It's meant to be interactive. Powershell is too heavyweight to be be a good daily driver for a shell.
- ygra 9y ago
  If you're after interactive use, then by all means define and use your own aliases (or functions) as you see fit. It'd be a pretty crappy idea to not do that. Custom aliases in scripts you share with others are not a good idea, of course, but that's firmly in the scripting aspect you note, not the interactive shell use. That being said, even with commands being long, tab completion does an absolutely amazing job of shortening what you type. Also it's usually just the first command of a pipeline that doesn't have an alias because after that you tend to use the same few cmdlets over and over again (%, ?, select, ft, ...), which do have short aliases.
- walljm 9y ago
  What do you mean by "not portable"? the alias script sits in a file and can be kept in source control, to be downloaded to any computer you land on. And many pw commands come with readymade aliases that are standard to the base install.

hungerstrike 9y ago

I too develop Node.js apps on Windows 10 and I'm with you - there is no reason to go out of my way to make it more Linux-like because everything just works. I use Cmd over PowerShell though since PowerShell can't process commands separated by "&&", which are used extensively in package.json scripts. I'm happy with this setup though since I don't think the CLI is a good interface at all (I prefer GUIs with lots of keyboard acceleration), so I tend to minimize CLI use as much as possible by automating everything down to single, simple commands. With VSCode, I can run my package scripts in the built-in terminal as well. Also, if I do have to edit some code on my Mac or Linux boxes (which I usually reserve for just compiling and testing things), VSCode gives me the same experience everywhere. I like that a lot!

pjmlp 9y ago

Me too, development is mostly done in .NET, Java and C++. Software that needs to be deployed on UNIX systems is usually written in Java. All the scripts that I need to access on both systems are written in Python. I rather make the best use of the tools each platform offers.

zaphar 9y ago

Powershell is an amazing shell scripting language. But it's a terrible daily driver of a shell. Everything is an enormously long line to type. Yes you can make aliases for common stuff but that's non-standard and not portable. The primary purpose of a shell is not scripting. It's meant to be interactive. Powershell is too heavyweight to be be a good daily driver for a shell.

ygra 9y ago
If you're after interactive use, then by all means define and use your own aliases (or functions) as you see fit. It'd be a pretty crappy idea to not do that. Custom aliases in scripts you share with others are not a good idea, of course, but that's firmly in the scripting aspect you note, not the interactive shell use. That being said, even with commands being long, tab completion does an absolutely amazing job of shortening what you type. Also it's usually just the first command of a pipeline that doesn't have an alias because after that you tend to use the same few cmdlets over and over again (%, ?, select, ft, ...), which do have short aliases.
walljm 9y ago
What do you mean by "not portable"? the alias script sits in a file and can be kept in source control, to be downloaded to any computer you land on. And many pw commands come with readymade aliases that are standard to the base install.