Microsoft’s releasing more open-source software, but, everyone knows it doesn’t matter if your distro doesn’t have a good shell.
This isn’t about how PowerShell sucks or how its source has been released under the MIT license so that naysayers can contribute the very features they believe are missing (or help address the over 1,800 issues open at the time of writing this blog post). No; this is about making PowerShell better with a Scoop.
Scoop is a command-line installer for Windows that was made to help make PowerShell a bit more digestible. Appreciating scoop requires a decent understanding of the context behind PowerShell and the Windows security system in general.
Microsoft, created PowerShell with cmdlets (
command-lets) - lightweight scripts that perform a single function - and created a Verb-Noun naming convention to help reduce command memorization. This is quite neat if you’re just getting started with terminals, shells, and Windows’ awkward brand of system administration - genuinely, I am a big fan of making things more accessible for new users.
Nothing’s clearer than a command that says,
Stop-Service, and it doesn’t take a senior SysAdmin to understand what a
Get Verb command might do to a Noun - good things I’m sure! However, the trade off tends to work against developers who do begin to memorize the more frequently used commands.
PowerShell’s are quite literally verbose. While some commands have aliases they aren’t necessarily the most familiar.
Get-ChildItem is listed as the command that, “gets the items and child items in one or more specified locations.” It’s aliases?
Most other commands, however, might be clear and transparent in meaning - but they lack any reasonable alias. No Unix developer is going to spend time configuring their aliases in Windows PowerShell when they can simply boot up Linux Bash on Windows.
Scoop helps by providing familiar tools from the bash environment and making them available to PowerShell. For example,
scoop install curl will allow you to use the
curl tool on PowerShell under your user account.
What does vanilla PowerShell do? It has aliased the
Invoke-RestMethod cmdlet as
wget while utilizing an entirely different syntax.
Don’t want to use the cmdlet? The related PowerShell commands aren’t much better:
Speaking of which…
Want to install something in Windows? I hope your pointer finger is ready.
When I’m not on the internet, I don’t expect pop-ups.
Introduced with Windows Vista, the User Account Control (UAC) is a part of Windows’ authentication and security suite. In the great scheme of things, this is the force behind the dialogue boxes that will interrupt your mojo whenever you try to make sure your installer isn’t employing any dark patterns.
There is no way to turn off UAC’s pop-up functionality on Windows. Scoop, however, is not like PowerShell and it certainly is not like Windows. It doesn’t concern itself with things that it doesn’t need to care about.
See, scoop understands something that all good Unix developers understand: you don’t need to sudo to install every little thing on your system.
I do not and I should not be giving administrative access and permissions to installers for most programs. Most applications don’t need to be installed to the
C:Program Files directories - there are many that can operate in a standalone (even portable) capacity.
Besides bettering your life, scoop is also a scriptable framework. It’s encouraged if you’re looking for a way to consistently setup environments on Windows systems that have access to PowerShell.
The original creator @lukesampson hasn’t submitted a new commit since mid-2017. At 787 commits, he still stands as the second biggest contributor.
The core developer, @r15ch13, on the other hand started in mid-2017 and now has over 5,610 commits.
It doesn’t take a git by a bus to see that the wealth of knowledge about this project is not distributed enough to keep it from perishing should @r15ch13 decide not to continue development.
Get it while you can.
You can find scoop’s source on its github repository.
Scoop is actually ‘licensed’ under the “Unlicense“. This is a specific way for developers to dedicate work to the public domain. The license itself combines a copyright waiver similar to that from the public domain SQLite project with the no-warranty statement from the MIT/X11 license.
It’s the antithesis to ‘all rights reserved’ - this license is a bit of a ‘no rights reserved‘ situation.
Since the time of writing, the last pull request was created 8 hours ago; it’s very active. In fact, the one disadvantage is that it’s become a burden on the current community.
GitHub contributor @h404bi submitted an issue last New Year’s Eve asking for the community to consider the fact that Scoop never releases a version that is ‘explicitly’ stable. The other developers agreed.
As it stands, they have yet to finalize a new workflow but their main challenge is separating the buckets - the name given to collections holding program installation settings and metadata - from the core of the program.
It’s a relatively small codebase and the documentation is more than enough for someone interested in getting started with how it works.
It is silly to realistically expect PowerShell to work like Bash. Even if the Verb-Noun dynamic gets tiresome, PowerShell is far from the only option available to users on Windows systems and people are always encouraged to use what they know best.
PowerShell is open-source; and so is scoop. These are both examples of what community development can support. The best part is the freedom to modify your environment however you see fit…
…That is, until you remember that Windows 10 is still a proprietary operating system and that nice OpenSUSE distro I have running a KDE Plasma desktop environment is sweet, sweet FLOSS.
After all things considered, perhaps it is with a bit of irony that in order to get scoop on Windows, you’ll need to be prepared to install it using plain old PowerShell.
iex (new-object net.webclient).downloadstring('https://get.scoop.sh')
(And you might come across a UAC error when you try this too).