libxo
PowerShell
| libxo | PowerShell | |
|---|---|---|
| 17 | 408 | |
| 337 | 47,888 | |
| 0.3% | 0.8% | |
| 0.0 | 9.7 | |
| 17 days ago | 7 days ago | |
| C | C# | |
| BSD 2-clause "Simplified" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
libxo
-
jc: Converts the output of popular command-line tools to JSON
> In FreeBSD, this problem was solved with libxo[0]:
Libxo happens to be in the base system, but it is generally available:
* https://github.com/Juniper/libxo
* https://libxo.readthedocs.io/en/latest/
- Libxo: The Easy Way to Generate Text, XML, JSON, and HTML Output
-
Getting work done with PowerShell on Linux
Or make it flexible:
> libxo - A Library for Generating Text, XML, JSON, and HTML Output
* https://github.com/Juniper/libxo/
* https://wiki.freebsd.org/LibXo
Want structure? Ask for JSON or XML and parse. Otherwise it's the regular text output.
- Libxo: Generate text/XML/JSON structured output in one code path
-
Jc – JSONifies the output of many CLI tools
Can you trust it? Cli tool output is not exactly stable. I thought that's why libxo exists?
https://github.com/Juniper/libxo
- Libxo: Library for Generating Text, XML, JSON, and HTML Output
-
Curl gets a --json flag
Please consider https://github.com/Juniper/libxo or something even better than that.
-
You shouldn't parse the output of ls(1)
That would look a lot like FreeBSD. Many of the FreeBSD userland tools are set up to use the excellent libxo (https://github.com/Juniper/libxo) to allow the user's choice of how things are output.
- The growth of command line options, 1979-Present
- Tips on Adding JSON Output to Your CLI App
PowerShell
-
Brush (Bo(u)rn(e) RUsty SHell) a POSIX and Bash-Compatible Shell in Rust
"can" is doing some heavy lifting there, especially based on my experience with VSCodium (which by definition is forced to work within Microsoft's opinion of build systems)
Anyway, uh-huh:
https://github.com/PowerShell/PowerShell/blob/v7.5.1/.github... -> https://github.com/PowerShell/PowerShell/blob/v7.5.1/.github...
https://github.com/PowerShell/PowerShell/blob/v7.5.1/.github... -> https://github.com/PowerShell/PowerShell/blob/v7.5.1/.github...
As a frame of reference, to build bash one only needs /bin/sh not a pre-built copy of bash itself https://git.savannah.gnu.org/cgit/bash.git/tree/configure?h=...
- PowerShell 7.5.0 Released
-
Fish shell announces 4.0 release
I'll take this moment to point out that the PowerShell feels like a modern shell and is open source https://github.com/PowerShell/PowerShell (MIT license). If you want something more modern give it a try. Native support for JSON and XML and parallel streams.
That said, I'm glad to see another major release of Fish because it's for having option that we get evolution.
-
Best PowerShell Dev Environment on Windows
Download: https://github.com/PowerShell/PowerShell/releases/download/v7.4.5/PowerShell-7.4.5-win-x64.msi
- PowerShell: Cross-Platform Automation and Scripting for Every System
- PowerShell for Every System: Cross-Platform Automation Made Easy
- Jeffrey Snover and the Making of PowerShell
-
Why *not* parse `ls` (and what to do instead)
PowerShell is so alien to an experienced bash/zsh/etc. user that it's an entirely different language not any kind of drop-in replacement. Its designers also refuse to add simple things to make the switch any easier (e.g. https://github.com/PowerShell/PowerShell/issues/3316).
-
Microsoft to Deprecate VBScript
Not necessarily:
1. UNIX-compatibility aliases like "ls -> Get-ChildItem" and "cat -> Get-Content" are not defined in PowerShell on Linux or macOS. For a complete list of these, see the PowerShell source code[1] (look for "#if !UNIX").
2. A number of aliases from PowerShell ≤ 5.1 were removed in PowerShell Core (≥ 6.0), including the particularly annoying "curl -> Invoke-WebRequest" (conflicts with curl.exe) and "sc -> Set-Content" (conflicts with sc.exe).
[1] https://github.com/PowerShell/PowerShell/blob/8ea1598964590b...
-
LuaRT: Lua programming environment for console, desktop applications for Windows
and do a no-install copy-paste deployment of powershell 7 and modules. (I'm not saying you should do this instead of using Lua, just that you can).
[1] https://github.com/PowerShell/PowerShell/releases
What are some alternatives?
PSScriptAnalyzer - Download ScriptAnalyzer from PowerShellGallery
nushell - A new type of shell
pdfalto - PDF to XML ALTO file converter
PowerToys - Windows system utilities to maximize productivity
jtbl - CLI tool to convert JSON and JSON Lines to terminal, CSV, HTTP, and markdown tables
xonsh - :shell: Python-powered shell. Full-featured and cross-platform.