Interestingly enough the issues you list seem related to capitalism rather than just any form of societal system.
Many literary utopias have non-capitalist systems but usually some sort of circular sharing system (some are outright communist, but others more slow living).
Greed must always be checked by a society. But since Calvinism we've had a dual moral reasoning (was that Charles Taylor or Hegel, can't recall). Through Calvinism capitalism attained the moral good of earning more than you need, to deploy greed for God.
Humans are naturally greedy (natural egoism is not immoral just a biological drive) and our political system should balance that out somehow.
I never could get used to jq's syntax so instead I've just been grepping. But this looks to be for jq what htop is to top, which is great for exploring response data.
IMO Python imports behave like the bash source command.
This is why people use the `if __name__ == "__main__"` so the majority of people will address it in all their scripts even if they don't know the reason why.
It's a feature not a bug IMO. You can use importing a .py file as a singleton hack. You can also use `refresh` to re-load a module, to clear it of any runtime overrides.
In my unqualified opinion the usability of e.g. phpBB forums (discussing through the browser) was much better than calling up a local BBS on telnet. Multilevel prompt menus in telnet can be quite maze-like.
Web crawlers indexed online forums too, so you could find the content right away through the same search engine instead of having to search the BBS discussions for hours or post a request on the local BBS and wait (days) for replies. Your technically illiterate aunt could browse the search results for posts containing the recipes she wanted from a number of disparate forums, and choose to read anonymously (and print out) or login and contribute. All you need is an email address.
This accessibility and semi-transparency created a major shift in where you go for content, effectively forcing the tech literate to follow suit as well. It fits in the general trend of democratizing the internet, and IMO was a good thing for tech. (I blame the monetizing and large commercial entities for the current state of fragmentation.)
I still login to a local BBS about once a year to say hello. Although I have a shell account now so I don't need to telnet over the net. It's still very alternative and hacker friendly.
While I appreciate the sentiment, I feel you're missing the point. This is akin to maddox's writing. It aims to strike a nice balance between satire and self-immolation, but might stumble in its attempts.
You're supposed to feel conflicted between the obnoxious tone and the rational message. The writing makes fun of know-it-alls while also making a well reasoned argument.
People who shout about ancient aliens and hidden technology always completely ignore that the people in the past had access to the most advanced machinery available: humans.
Add time to that, so that your project can have a scope of generations, passing down knowledge gained from a lifetime of doing this particular thing, the results become unsurprising even.
Amazing, inspiring and ingenious but also unsurprising.
As a self-taught coder, I've experienced many times how highly skilled software engineers groan and sweat when they encounter shell scripts. I don't understand why, but it seems like people with a CS background are never really taught shell scripts and have come to irrationally fear them. It's sort of taboo.
This results in weird behavior, such as writing a groovy (Java?) script for Jenkins to execute bazel in order to build a go binary that runs the very same commands in an exec.Command() construct. Or people who download and import pandas to grab the third field in a csv file.
During the course of learning, I've naturally written code in bash that should have been written in another language. I replaced if statements with case because they turned out to be more performant. It's a great learning experience and why I got into python and go.
IMO we should use the right tool for the job. Sometimes that tool is a combination of unix utilities that you can put in a shell script for easier maintenance. It's just procedural execution of (usually very efficient) binaries, akin to a jenkins script or gitlab pipeline. Just mind the exceptions and use exit codes.