I think the takeaway for me is that emacs is for people who get enjoyment out of building their own custom computing environment
The example you describe is something I would rarely do so building a process around it would be inefficient for me but if that’s where people want to spend time then great
> The example you describe
It's just a drop in a vast ocean of things. Your close-minded thinking just sees one thing and makes generalized assumptions.
> where people want to spend time
You're reading it completely backwards. This is the thing that I never understood about the majority of programmers. For whatever reason they just readily accept the status quo. Here's a typical example:
So often do I feel like rolling my eyes whenever I pair with my colleagues - I'd do something trivial, like fetching a list of PRs related to a specific ticket number at the cursor. They'd be like "whoa, that's cool", and then never do anything about it - they stick to their "learned helplessness" paradigm - copy the ticket number, switch to browser, navigate to Jira, pass through SSO, look around for the phone just to push the button, paste the ticket number, find the linked PRs, etc. The other teammate watching all that may say something like: "you could do it faster directly on GitHub"... And here I am - pressing a key, voila - the list. Why the heck don't they do anything about it, I just don't get it. Trained engineers, they spend years dealing with cranky software, why in the world are they unwilling to do anything about these seemingly small yet everyday annoyances? Why do so many programmers treat software as if it's magic? And I think I know the answer: because the software you use shapes your affordances. If there's no downloadable get-me-list-of-prs-for-a-jira-ticket VSCode extension and no simple way to build it, it would never occur to them to even get annoyed. In Emacs, I can write a picker in a scratch buffer by hand and it would take me minutes. Today with LLMs, I can just spend fifteen seconds, not even typing, speaking my thoughts and it goes to build it, run a sequence of e2e tests and hand it to me on the spot.
Sure, go ahead, talk about time. Make me chuckle. The irony is that the time you spend using a Lisp-based system never feels wasted; it only gets better, it has a compounding effect. It's the time you waste convincing skeptics that it is in fact enormously pragmatic and time-saving that feels like tilting at windmills. Why am I even still talking to you here, if it was clear from the beginning that you didn't in fact have good-will curiosity, only simply wanted to find evidence for your already settled and stiffened mind.
You think people choose and stay with Emacs, because their parents baptize them into it? It's a hands-down the best known system to deal with text of any kind. It is not a text-editor, text-processor, IDE or coding tool. It's an effing text orchestrator. It is capable of handling multitude kinds of text-related tasks in anything in its computational vicinity - local and remote computers, apps, and services. And programming is all about text. That is the essence that every computer user has to conquer first and foremost; everything else is secondary.