electricEmu

In the following example, 'choco' (Chocolatey) outputs a list of outdated packages in a consistent format (--limit-output). The text output is piped to the ConvertFrom-CSV PowerShell CmdLet, which maps the text output from choco into a PowerShell object.

```ps1 choco outdated --limit-output | ConvertFrom-csv -Delimiter '|' -Header 'name','version','v-new','pin' ```

For what it's worth, STDERR is already colorized in PowerShell too.

Comment · 5 years ago

WSL on Windows replaces the need for uutils/coreutils. Running an actual distribution of Linux on Windows with WSL provides an actual Linux/POSIX environment.

In my experience, there is a graveyard of tools that I tried which attempted to create native POSIX ports for Windows. Each port came up short in my workflow every time. PowerShell and WSL provide me and the teams I work with an experience that simply works.

Comment · 5 years ago

PowerShell also runs on Mac, Windows, and Linux. You pass objects instead of plaintext through the pipeline which provides a rich experience. The full .NET type and ecosystem are also available when you really need a full fledged class for a thing.

There are good choices in 2021.

https://docs.microsoft.com/en-us/powershell/scripting/instal...

Comment · 5 years ago

POSIX commands are available on *nix platforms and PowerShell provides native functions or POSIX wrappers for most tasks. About the biggest issue is speed, but there's always POSIX or .NET Core in the rare instance tons of performance is required.

If I may, PS is a first-class citizen on Linux, macOS, and Windows. PowerShell is a spectacular cross-platform shell that provides an object oriented paradigm and it's available today.

Comment · 5 years ago

PowerShell runs on Linux. I run PS as my primary shell [0] on Linux today. It's is open source too.

You're not far away with how PowerShell can parse Linux commands. Instead of relying on awk/grep, PowerShell uses .NET under the hood to provide consistency across operating systems. There are a few methods for converting from a Linux command to PowerShell objects based on delimiters or OFS. If you're interested, Steve Lee wrote a blog post that does a good job covering how to parse Linux command output into PowerShell objects [1].

[0] https://docs.microsoft.com/en-us/powershell/scripting/instal...

[1] https://devblogs.microsoft.com/powershell/parsing-text-with-...

Comment · 5 years ago

For years I've watched the rivers in Washington State receive consideration. Progress has been made and continues to be.

Saying humankind has done "nothing" is not only mistaken, but makes for poor conversation. Perhaps more people should take a page from Attenborough.

https://www.spokesman.com/stories/2020/dec/17/for-the-first-...

Comment · 6 years ago

Small trucks may cut enough emissions by reducing road-wear. If everyone switched from large trucks to an even larger amount of small trucks it's possible the problem is made worse.

Why the focus on small trucks as if they're a panacea?

Comment · 6 years ago

Honestly, it's good to hear I'm not alone.

Synchronization in Joplin concerned me too. E2EE is non-trivial to setup and Joplin will upload decrypted files if E2EE is misconfigured on a device. Encryption appears to be an afterthought in Joplin.

Standard Notes looks snazzy but too many features fail to work. I cannot get paste to work consistently on my mobile devices, and you're right - the editors are a an absolute mess. File Safe is only supported in unsupported editors and the supported editors lack basic features. FYI, the spreadsheet editor unsupported and exporting sheet data is...difficult.

I do not recommend Standard Notes anymore. Thanks for pointing out a need for external backups in Joplin though!