Same for me. The "pipe streams of text" is so very powerful, I doubt anything can replace it.
Obviously, the "streams of text" need to make sense and have somewhat consistent structure - which most older tools don't really do - some mix tabs and spaces, others offer very little consistency between e.g. --verbose and normal. And modern ones often forego entirely. I hate it that docker pumps giant datastructures of JSON. And jq helps a lot there. Or ansible that has genormous blobs of json, mixed with yaml placed inside - I kid you not, cowsay - outputs. What I really want is just text, that I can minimize with flags and is delimited with spaces and newlines, so that a grep, cut, sed, sort, uniq, and, if all else fails, awk, can map/reduce me the data I need.
Simple text streams. If we can have that, we can bind everything togethe and "build" IDE features that no IDE can offer me without severe programming, plugins or other shenanigans.
Some things that I did this month, that I have no idea if VS code or Jetbrains can do:
- git log --format=format: --name-only | grep -v '^$' | sort | uniq -c | sort -nr | head -n 10 # Give me the 10 files with the highest churn - most often edited so potentially most problematic ones.
- < dev.log | grep "WARN:" | cut -d " " -f 2- | sort | uniq -c # List all warnings most occurring at the top.
- git log --reverse --pretty=format:"%H" | while read commit_sha; do
git checkout "$commit_sha" -- .
./lint.sh 2>> linting.log
done
# Loop through all commits to record all linting violations so to find commits with exceptional amounts of linting violations.
Same for me. The "pipe streams of text" is so very powerful, I doubt anything can replace it.
Obviously, the "streams of text" need to make sense and have somewhat consistent structure - which most older tools don't really do - some mix tabs and spaces, others offer very little consistency between e.g. --verbose and normal. And modern ones often forego entirely. I hate it that docker pumps giant datastructures of JSON. And jq helps a lot there. Or ansible that has genormous blobs of json, mixed with yaml placed inside - I kid you not, cowsay - outputs. What I really want is just text, that I can minimize with flags and is delimited with spaces and newlines, so that a grep, cut, sed, sort, uniq, and, if all else fails, awk, can map/reduce me the data I need.
Simple text streams. If we can have that, we can bind everything togethe and "build" IDE features that no IDE can offer me without severe programming, plugins or other shenanigans.
Some things that I did this month, that I have no idea if VS code or Jetbrains can do:
- git log --format=format: --name-only | grep -v '^$' | sort | uniq -c | sort -nr | head -n 10 # Give me the 10 files with the highest churn - most often edited so potentially most problematic ones.
- < dev.log | grep "WARN:" | cut -d " " -f 2- | sort | uniq -c # List all warnings most occurring at the top.
- git log --reverse --pretty=format:"%H" | while read commit_sha; do git checkout "$commit_sha" -- . ./lint.sh 2>> linting.log done # Loop through all commits to record all linting violations so to find commits with exceptional amounts of linting violations.