3 ms·

Microsoft was also a long time anti-commandline and against scripting, they tried to made everything clickable, with wizards and s**, and remove text and keyboa

Microsoft was also a long time anti-commandline and against scripting, they tried to made everything clickable, with wizards and s**, and remove text and keyboard-input as much as possible for admins and devs. Thinking about, Copilot is in it's own way, a continuation of this, just more dev-friendly.

bradford 4y ago
> Microsoft was also a long time anti-commandline and against scripting, they tried to made everything clickable, with wizards and s*, I'd categorize this as incompetence, not malice towards developers. Specifically: Microsoft thought that code-creation wizards and UI would offer a better story than command line and text. Those attempts were misguided, and MS adjusted. The command line culture at MS has been pervasive for a long time, despite the quirkiness of DOS, so I must object to your categorization of MS being anti command-line and anti-scripting. [disclaimer, MS employee, my opinion only.]
klibertp 4y ago
Yeah, but then they made PowerShell, which was at the time seriously the most advanced shell and shell scripting language out there. PS got pretty mixed reactions because it was different than BASH, but the idea of typed pipes of objects instead of one-size-fits-all streams of lines of text was (and still is) powerful. (The syntax could be a little less verbose though)
DeathArrow 4y ago
Being a developer isn't the same as being a command line user. Most Windows users prefer GUI over the command line. That being said, Microsoft released PowerShell, Windows Terminal and lots of command line tools. A large part of the Windows administration can be done trough command line if one so desires.
int_19h 4y ago
Even during the 90s, arguably at the peak of "make everything GUI", this was also a thing in Windows: https://en.wikipedia.org/wiki/Active_Scripting https://en.wikipedia.org/wiki/Active_Scripting

bradford 4y ago

> Microsoft was also a long time anti-commandline and against scripting, they tried to made everything clickable, with wizards and s*, I'd categorize this as incompetence, not malice towards developers. Specifically: Microsoft thought that code-creation wizards and UI would offer a better story than command line and text. Those attempts were misguided, and MS adjusted. The command line culture at MS has been pervasive for a long time, despite the quirkiness of DOS, so I must object to your categorization of MS being anti command-line and anti-scripting. [disclaimer, MS employee, my opinion only.]

klibertp 4y ago

Yeah, but then they made PowerShell, which was at the time seriously the most advanced shell and shell scripting language out there. PS got pretty mixed reactions because it was different than BASH, but the idea of typed pipes of objects instead of one-size-fits-all streams of lines of text was (and still is) powerful. (The syntax could be a little less verbose though)

DeathArrow 4y ago

Being a developer isn't the same as being a command line user. Most Windows users prefer GUI over the command line. That being said, Microsoft released PowerShell, Windows Terminal and lots of command line tools. A large part of the Windows administration can be done trough command line if one so desires.

int_19h 4y ago

Even during the 90s, arguably at the peak of "make everything GUI", this was also a thing in Windows: https://en.wikipedia.org/wiki/Active_Scripting https://en.wikipedia.org/wiki/Active_Scripting