gerrard00

I definitely think this should be opt-in but I also think that it's silly to focus on just this scenario. I'd bet dollars to doughnuts that Google Docs and every other web based business tool use similar telemetry data to guide their UX and product investments as well as to preemptively address bugs.

Which allows them to determine exactly the best way to do that for their purposes. I just run the command and it magically works.

It'll be a long time before the Powershell ecosystem has a fraction of tools that are compatible with it's .NET object pipeline.

I used Powershell extensively before I ever had experience with a linux or unix shell. I still have more experience with Powershell than bash or zsh, but I can't imaging going back. I'm already much more capable in a *nix shell.

There are advantages to having a pipe based on structured data, but that also means you have to know what structure to expect at ever step of the way and whether or not other tools can work with that structure. There are also tons of little quirks about Powershell; enough so that I eventually just started writing most stuff in C# and then just using the Powershell scripts as glue.

Passing text means that every single one of the thousands and thousands of unix cli tools that accept stdio will work in your pipeline.

I think this industry needs to get away from the terrible/horrible, absolute thinking. Most tools have positive and negative

I don't think they deserve empathy at all. If they can't implement the feature to the level of being usable they should just cut the feature instead of annoying the user.

So much software development today is about getting story points on a velocity chart and claiming that features have been delivered even if the feature is actually useless. A Minimum Viable Product should actually be viable.

Most Vim users I talk to have remapped CapsLock or another set of keys to escape, since the escape key is so far away. I personally use `jk` since I rarely write anything with Dutch names.