|
I wonder for a while they tried to kill the DOS prompt and failed is power shell the sorry, or just a 'new' product.
|
|
|
|
|
PS is hardly "new", it incorporates cmd, and is infinitely better from an SA standpoint, AKA the people that actually use the CLI in Windows. Your issue is what, exactly?
"Never attribute to malice that which can be explained by stupidity."
- Hanlon's Razor
|
|
|
|
|
50% legacy
50% *nix hackers (and that's why the legacy percentage is so high)
The higher education in software technology has been touting Windows as a toy OS for 30 years, and they still do. Real Developers Use Linux. And Linux tools.
The main reason why Linux hasn't taken over completely is that those amateurs using Windows are unwilling to learn anything new; they simply are not intellectuall capable to handle the list of gcc options, the regex syntax of find etc. They just won't learn anything new! Look at this primitive cmd.exe - bash was a thousand times more advanced than that the day Windows was born! (Are you really trying to argue that Windows was born before bash?? That's exactly the kind of false claims you can make the Windows congregation believe in!)
So there is a socalled "advanced" shell for Windows ... Blah! Can it run bash scipts? No! So how can it be "advanced", when it cannot run decent scripts? If you are asking me to spend resources to some silly Microsoft-thing that is nothing more than a simple patch-up of that DOS-toy-shell, then just forget it! I cannot spend time on learning anthing as useless as a non-Linux tool, when my Linux tools can do the job!
... Maybe I am exaggregating a little - but just a little. Our company policy is that desktop PCs run Windows; we have build and test machines running Linux, that you can remote in to, for the part of our work that is Linux based. We are establishing a Docker environment for Linux flavor containers nowadays; the Windows Docker engine may build and run Linux flavor docker images perfectly well. But that cannot be used by those Linux Real Programmers: It turns out that they have installed virtualization techniology on their desktops for the sole purpose of running Linux utilities in a Linux environment - utilities that have perfectly fine parallels in the Windows environment, with company support. Then they would have to learn a utility that they never saw in their studies, and learning something new that is outside Linux is a waste of resources.
They spent so much time to make this open-source virtualization run under that silly Windows, that they don't have time for more. And that open-source VM competes with the Microsoft Hyper-V for certain system resources, and Hyper-V is required for the desktop Docker installation. We are sorry about that. We simply cannot use Windows Docker on our desktops, without giving up our beloved Linux utilities.
But hey, we can run a Linux Docker engine on that VM we have installed to run those Linux utilities - then we can run Docker on the desktop!
... and so, rather than learning Windows utilities, including PowerShell, and updating the scripts to PS, they move the whole thing over to that VM so they can use Linux bash instead, during their daily work. For Python projects, that is more or less doable. The "official", company supported setup is still Windows, but since cmd.exe is so primitive, it is better to "secretly" use bash on VM under Windows than learning to use non-primitive MS tools. After all, Windows is just for kids, so why care?
[End of rant]
|
|
|
|
|
You talk about Windows being a kiddie's operating system in one breath, then talk about using Python in the next. 
As someone who has developed on both UNIX and Windows, I can assure you that it's hardly a case of one being trivial and the other non-trivial, or one being great and the other being crap - it's simply a case of them being different things.
Yes, when I first moved to Windows as a primary development platform, I certainly missed the Bourne and Korn shells and maybe they do offer some of the inspiration for Powershell but Powershell is not just some simple exercise in recreating the glories of 1970s UNIX shells, it very much moves it in to the OO world. It's a million miles away from the traditional Windows command shell and actually rather a wonderful thing.
Whenever you find yourself on the side of the majority, it is time to pause and reflect. - Mark Twain
|
|
|
|
|
Cool story, brah.
Member 7989122 wrote: So there is a socalled "advanced" shell for Windows ... Blah! Can it run bash scipts? No! So how can it be "advanced", when it cannot run decent scripts?
This is the funniest thing I've read in ages. Thank you!
"Never attribute to malice that which can be explained by stupidity."
- Hanlon's Razor
|
|
|
|
|
I found it irritating at first that without my consent Command in the Windows Start menu was replaced by Powershell, but it seems unavoidable and it's best to get used to it ...
|
|
|
|
|
You can easily switch it back to Command Prompt: Control Panel -> Settings -> Personalisation -> Taskbar.
|
|
|
|
|
I know, I did that and on the next Windows update it was reset to PowerShell again. So now I have "seen the light" and started using PowerShell, just do not go against the Microsoft flow 
|
|
|
|
|
I have tried using it but my slow old brain struggles with new stuff. So Command Prompt still holds me in thrall.
|
|
|
|
|
Richard MacCutchan wrote: So Command Prompt still holds me in thrall.
Right there with ya, Richard. I recently showed my college-age son the wonder of a customized prompt in the Command window. I did not know eyes could get so big! 
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
|
|
|
|
|
I remember showing a young guy at work how to use a Hollerith card punch. He could not understand how the holes were read as characters.
|
|
|
|
|
I always thought that PowerShell was a piece of armor I would get when I reached level 120. Well, I have been at level 120 for a while now, and I don't see no damn PowerShell. 
|
|
|
|
|
|
Well, it is not everyday that one finds something that they can trust. Seem that Bacofoil has the strength that I can trust.
I am sure that it will make a nice hat as well. 
|
|
|
|
|
PowerShell editing with Visual Studio Code[^]
I started using Visual Code for my Unity game development, and noticed that it also can be used as a terminal\editor for PowerShell scripts, etc. It appears that it has some nice features too, for this. Worth a look I think.
modified 6-Mar-19 9:11am.
|
|
|
|
|
This is also available for Visual Studio,
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
yes, it is.
If he has VS community/pro, then great. if not Visual Code is much more light weight editor.
|
|
|
|
|
The one (huge) benefit of PowerShell over Bash (IMNSHO): You're working with actual objects, with properties and methods, rather than just parsing strings. Just about anything in .NET that's public can be invoked.
As for your longer rant (elsewhere in this thread): Are you aware of WSL? It's not merely a VM or a re-implementation of existing commands like Cygwin.
|
|
|
|
|
You can access your own .NET dll's as well. It's pretty damn snazzy.
"Never attribute to malice that which can be explained by stupidity."
- Hanlon's Razor
|
|
|
|
|
Pretty much any .NET DLL.
A few years ago I started poking around one of my DLLs with PowerShell, just for the fun of it, and started scripting some things using some of my classes that were never meant to be scripted / for scripting.
Some "feature" I wrote with PS became something a customer wanted us to implement, but management saw little very value in us implementing it right in the program - so the customer got it as a PS script.
|
|
|
|
|
They'll be blocking/restricting access to it soon here. 
|
|
|
|
|
glennPattonWork wrote: So Power Shell...basically Bash for MS?
Not that I have seen.
glennPattonWork wrote: gives proper access to previous commands like Doskey
I haven't had any problem creating scripts on windows that do basically the same thing that I do with bash scripts for quite a few years.
Same problems with both for example running programs that do not in fact return a non-zero exit code when there is an error. Or sometimes programs exist on one but not the other.
But perhaps just because I am not looking to automate the world with bash/dos scripts but rather just automate a bit of repetitive typing and get on with what I am actually supposed to be doing.
|
|
|
|
|
Humble Book Bundle: Computer Science by Mercury Learning (pay what you want and help charity)[^]
26 books on topics going from AI and Data Mining to 3D programming, OpenGL, Python, C, Photoshop and a kton of other things. 15 bucks. Take a look if you're interested!
Sorry for the spam-like message but I think it would be criminal to withold this information from the CP community.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
|
Man, you seem Hyperactive!
"If we don't change direction, we'll end up where we're going"
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
