Live data from Hacker News

More, less, and a story of typical Unix fossilization

utcc.utoronto.ca

121–127 of 127 posts

Re: More, less, and a story of typical Unix fossilization

#121

Earlier quoted context omitted.

Oh I actually did know about the package manager, but I didn't know that that's coming to *NIX through PowerShell. For reference: https://blogs.technet.microsoft.com/packagemanagement/2015/0... If I remember well, some time ago MS announced that on Windows you would be able to use Chocolatey as an additional source, which I thought was interesting.

PowerShell itself now has a packaging system and public repository for modules: http://www.powershellgallery.com/ PowerShell for Windows got this earlier in the year, and it's part of PowerShell Core. So with PS Core, you should be able to start a freshly installed copy of PS on whatever OS you are using, and add the AWS modules with this command: Install-Module AWSPowerShell.NetCore (Warning: this command does not w…

Thanks, I had a look and it's interesting, do you know if the Power Shell Library is just a distribution channel based on the Win 10 package management system that I linked in my previous comment, or is it a completely separate product?

Re: More, less, and a story of typical Unix fossilization

#122

Earlier quoted context omitted.

PowerShell itself now has a packaging system and public repository for modules: http://www.powershellgallery.com/ PowerShell for Windows got this earlier in the year, and it's part of PowerShell Core. So with PS Core, you should be able to start a freshly installed copy of PS on whatever OS you are using, and add the AWS modules with this command: Install-Module AWSPowerShell.NetCore (Warning: this command does not w…

Thanks, I had a look and it's interesting, do you know if the Power Shell Library is just a distribution channel based on the Win 10 package management system that I linked in my previous comment, or is it a completely separate product?

AIUI, PackageManagement really is literally just a convenience API for providing a consistent set of calls for driving arbitrary package management systems, and has no package management capabilities at all itself. It's actually not Windows-specific.

The actual package management system for PowerShell modules is PowerShellGet.

On Mac, PowerShell Core includes PackageManagement, and two "providers" - an adapter for PowerShellGet and one for NuGet, so you seem to be able to do either:

Find-Module AWSPowerShell.NetCore

(to use PowerShellGet directly)

Or:

Find-Package AWSPowerShell.NetCore

(to go through PackageManagement)

Re: More, less, and a story of typical Unix fossilization

#123

Earlier quoted context omitted.

PowerShell itself now has a packaging system and public repository for modules: http://www.powershellgallery.com/ PowerShell for Windows got this earlier in the year, and it's part of PowerShell Core. So with PS Core, you should be able to start a freshly installed copy of PS on whatever OS you are using, and add the AWS modules with this command: Install-Module AWSPowerShell.NetCore (Warning: this command does not w…

Thanks, I had a look and it's interesting, do you know if the Power Shell Library is just a distribution channel based on the Win 10 package management system that I linked in my previous comment, or is it a completely separate product?

The actual package management system for PowerShell modules is PowerShellGet. AIUI, PackageManagement really is just a convenience for providing a consistent set of PowerShell commands for driving arbitrary package management systems, and has no package management capabilities at all itself. It's not Windows-specific, and seems to have been made cross-platform with PowerShell itself.

On Mac, PowerShell Core includes PackageManagement, and two "providers" - an adapter for PowerShellGet and one for NuGet, so you appear to be able to do either:

Find-Module AWSPowerShell.NetCore

(to use PowerShellGet directly)

Or:

Find-Package AWSPowerShell.NetCore

(to go through PackageManagement)

I didn't know most of this until I started poking around, so thanks for asking!

Re: More, less, and a story of typical Unix fossilization

#124

Earlier quoted context omitted.

Thanks, I had a look and it's interesting, do you know if the Power Shell Library is just a distribution channel based on the Win 10 package management system that I linked in my previous comment, or is it a completely separate product?

AIUI, PackageManagement really is literally just a convenience API for providing a consistent set of calls for driving arbitrary package management systems, and has no package management capabilities at all itself. It's actually not Windows-specific. The actual package management system for PowerShell modules is PowerShellGet. On Mac, PowerShell Core includes PackageManagement, and two "providers" - an adapter for Po…

Urgh, double-post and no edit or delete options - thanks, HN.

Re: More, less, and a story of typical Unix fossilization

#125

I can see the fossilization, but I don't see what's so typical Unix of that phenomenon. Windows still includes cmd.exe with all its broken, retarded features, while it has powershell, which is supposedly (no experience myself) a little less retarded.

But that was originally command.com, to command.exe to cmd.exe There is no "edit" or "edlin" any more or "ftp" or "telnet" or "tr" :(

There was never, to my knowledge, a command.exe .

Re: More, less, and a story of typical Unix fossilization

#126
post #50

I don't believe more is the first Unix pager - doesn't pg predate it? IIRC pg is the only pager required by POSIX.

pg and the System 5 side of things are notable by their absence from M. Siebenmann's article. But pg appeared in System 5 release 2 or (more probably) 3 whereas more was 3.0BSD.

Re: More, less, and a story of typical Unix fossilization

#127

Earlier quoted context omitted.

AIUI, PackageManagement really is literally just a convenience API for providing a consistent set of calls for driving arbitrary package management systems, and has no package management capabilities at all itself. It's actually not Windows-specific. The actual package management system for PowerShell modules is PowerShellGet. On Mac, PowerShell Core includes PackageManagement, and two "providers" - an adapter for Po…

Urgh, double-post and no edit or delete options - thanks, HN.

Thanks for the (double :-) ) explanation! This kind of capability in PowerShell is definitely interesting.
Post reply on HN