MIT licensed.

https://learn.microsoft.com/en-us/powershell/scripting/insta...

The artists criticizing Mr. Musk make a good point about what's really happening.

https://youtu.be/i9qWYUH5x3k

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.

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.

There are good choices in 2021.

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

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.

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-...

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-...

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

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!

I am interested in using Joplin exclusively and use both apps currently. The Standard Notes development team is nice but refactors happen too frequently and estimates are rarely (never) produced, even though the product is paid Open Source.

Here, a multi-racial family was menaced by residents of Forks, WA. Residents actually cut down trees to block the road.

https://q13fox.com/2020/06/05/spokane-family-harassed-strand...

Here, a police offier's relative drove into the protests, shot a protestor, and ran to the police station.

https://www.washingtonpost.com/nation/2020/06/08/seattle-sho...

While these instances are not widespread, they are incredibly troubling.

DDB is great for storing data that is required to be scalable and never needs to be joined. Add in DAX, developer time necessary to orchestrate transactions, calculate the scaling costs and...that's how AWS gets you.

Plus, local development requires half-complete emulators or a hosted database you're charged for.

No, maybe people should think twice about DynanoDB.

Yes, it's possible to rsync flat files from Dokuwiki to somewhere else, but Dokuwiki files are stored in a unique format. Moving files from one machine to another does not make the format more ubiquitous or easier to parse. The amount of work required to migrate data out of Dokuwiki may be trivial to some very experienced developers but would be neigh impossible for greener developers.

The plugin ecosystem of Dokuwiki is reminiscent of Jenkins. Dokuwiki plugins can do anything, but few seem to do them well or without quirks. Some require updating the CSS and HTML template for a theme. Others require modifying the host system. Few plugins are active, modern, and useful to more than a subset of specialized scenarios. The mobile editors are truly an exercise in frustration for even tech-savvy users.

Dokuwiki is great if you have specialized needs and accept the file format costs. The specialized markup language and plugin ecosystem are a type lock-in that should really be stated more up-front to new and perspective Dokuwiki users. I do recommend Dokuwiki for very particular and specific needs, but not as a general purpose wiki for "most people".

My primary driver for seeking out a new wiki was because of how difficult testing and managing Dokuwiki can be. Updates to the main wiki are infrequent, plugins are often abandoned, and the setup, running, and maintained of the wiki is non-trivial.

I recommended wiki.js is easier to run, uses markdown by default, backs up data as flat files in a git repository, and does not require many resources either. Plus, there's a supported Docker image that works out of the box.

There's no problem with choice. Dokuwiki is frequently recommended to new users and wonder if that wiki is an appropriate recommendation. I explicitly would suggest wiki.js or something similar to someone not already running Dokuwiki.

I am happy with wiki.js. It's much less maintenance than Dokuwiki.

Why choose the exurbs where you pay a premium to drive long distances and live far away from opportunity and medical care? Plus, exurbs were some of the hardest hit during the '08 recession [1].

> But underlying today’s exurban fervor is an uncomfortable truth: The reason that homes in these communities are so affordable is that these areas were among the hardest-hit by the housing crisis and recession, and prices have only recently recovered.

Recessions are very difficult to predict. Maybe it will be some time before a reckoning in the exurbs comes due again.

[1] https://www.marketwatch.com/story/it-can-be-risky-to-buy-a-h...

Your original assertion was renters will move because the city is unsafe during COVID and that suburan areas are worth the price to commute trade-off.

Two suburban areas around Seattle are Snohomish and Pierce counties. Those "safer" suburbs are doing an objectively worse job of following Washington State's "Stay at Home" order [1]. Prior to COVID, hospitals were closing in rural and exurban areas, which reduced capacity during this pandemic [2]. Disregarding SAH/SIP orders and reduced capacity sounds dangerous, not safer and worth saving money.

As for cost, when enough housing capacity was built in Seattle then the rent stabilized. After short-term rentals are converted back into single-family homes or long-term leases then rent should continue to stabilize or decrease. When I last looked, increasing my commute from 25m to over 1h was not worth the savings in rent and would have required purchasing a car.

It's great you prefer the suburbs and there are absolutely people the 'burbs are better suited. Unless you have a valid reason to suggest people are going to move in-mass from cities to the burbs then I find "diminished city living" mistaken and comical.

[1] https://www.unacast.com/covid19/social-distancing-scoreboard... [2] https://www.npr.org/2020/04/09/829753752/small-town-hospital...

As for space, cities have lacked space for as long as cities have existed but people continue to migrate for the opportunity. I wouldn't be surprised if housing prices drop from short-term rentals reentering the market as single-family homes or long-term rentals.

The decision is not so clear cut.