The idea is to make builds (more) reproducible. I can build a python program, test it thoroughly, and then be reasonably assured the whole thing won't come crashing down in CI/CD from a bad update to a transient dependency. Then when I want to update the libraries I know I'm doing it purposefully and can commit the new dependency tree to source control.
pipenv does more than just create a venv, although it is my favorite tool for that. The most important thing it does is freeze the dependency tree using Pipfile.lock
To be specific, what is disallowed is using technology to steal signs (the camera). You can steal signs if there is a runner on second, although the pitcher and catcher can then change signs. It's one of the 'unwritten rules' in that it happens but they try to be sneaky about it. You don't want to disrespect the other team. More often with good scouting hitters can get an advantage of the pitcher is 'tipping the pitch', i.e. using a different delivery or setup depending on what pitch is coming. For instance, how high they hold the glove
A small correction, stealing signs is not disallowed, and pitchers and catchers will have different sets of signs they use when there is a runner on second base. What is disallowed is the use of technology to steal signs, the camera in center field going to the TV behind the dugout
"The Art of Memory" by Frances Yates is an interesting and scholarly book on the ancient origins of this idea. It's not a light read but I find it fascinating how influential this idea has been over such long periods of time, and also how memory has changed and evolved with the accessibility of the written word. Reciting hour long speeches word for word from memory used to be a commonplace skill (rhetoric).
I'm not sure I understand your example. Emacs integrates, it doesn't need to be integrated. It also has the best git interface I have ever seen (magit).
In a certain sense a subclass of Emacs users are the makers since it is a traditional Free Software model not backed by a major corporation. But that can be seen as an advantage since there is no single point of failure, and if GNU doesn't do a good job it can be forked, and has in the past (remember XEmacs?).
Practically speaking, the major disadvantage of Emacs is poor asynchronous/ multithreaded support. That's not an easy problem to solve but I do think it will get better eventually, and I don't find it a major impediment in day-to-day use.
That's a strange thing to say. GNU Emacs has been around 33, years, is still very actively developed, is GPL so could be forked, and seems more popular than ever. You don't have to justify your decision to not use Emacs by saying Emacs has a bleak future. I think Emacs probably has the most secure future of any text editor or IDE.
In the author's defense, I came to the same conclusion using Dvorak when I was a teenager learning unix and programming. I switched back to QWERTY for a while, but around 8 years ago I learned about Colemak and switched and have been very happy with it since.
One thing I like about Colemak is that it is close enough to QWERTY that I can still type on QWERTY by looking at the keys and not look like a complete fool. Dvorak is so different that it completely rewires the brain and it's very difficult to switch between it and QWERTY. That's been my experience at least.
What's interesting is that LaserDisc (the optical ancestors of DVDs that look like giant CDs) are analog. The video and audio streams are encoded with Pulse Width Modulation (PWM)