5 ms·
> And, as of Powershell 2.0, you have remote scripting similar to SSH. What, instead of actually using the ubiquitous, widely installed SSH? Some things don't
by mhw 16y ago
> And, as of Powershell 2.0, you have remote scripting similar to SSH.
What, instead of actually using the ubiquitous, widely installed SSH? Some things don't seem to change.
- code_duck 16y agoThat's my problem with PowerShell. No matter how good it may be, I don't really feel like relearning everything just to accomplish the same things, only on Windows instead.
- yread 16y agoAre you sure you are in the right business if you don't like relearning?
- vetinari 16y agoYes, throw away everything you know every now and then, instead of building knowledge on top of knowledge. That will get you far, right?
- mey 16y agoWho says you have to throw away everything you know? I don't magically stop knowing C++ when running around in Ruby or SQL.
- jpr 16y agoLearning new stuff is cool. Relearning same old stuff in different clothing because someone decided to do something differently is not cool.
- contextfree 16y agoPS is substantially different enough that I don't mind, though.
- code_duck 16y agoI like relearning. I don't have much use for re-learning... I'd rather learn to do something new. The "to accomplish the same things, only on Windows instead" is the crucial qualifier. I'd rather spend my time, I don't know - learning to configure nginx or doing Haskell tutorials than learn someone's proprietary shell, given that shells aren't particularly exciting and I already know enough about the shells that every other platform offers to be satisifed.
- euroclydon 16y agoI'm right there with you not wanting to learn a new shell, however PS is written against the .NET Windows API. The new stuff you'd have to learn would be Windows specific, sort of like learning AppleScript. Also, PS has traditional unix shell commands built in now, like grep and ls.