Re:Literate DevOps
by zelphirkalt on Sunday August 30, 2020 @11:04AM
(#24323353)
So your point is, that org mode is just inside one tool and therefore one cannot expect everyone else on the team to learn it?
I think we can make the same argument for every single tool out there, like one specific IDE or whatever you have. It's just a question of how many people already use Emacs on the team, to make a democratic decision.
Or is there some criteria, by which I can sort tools into 2 camps, "OK to force upon coworkers" and "not OK to force upon other coworkers"?
[ Parent
| on HN ]
Re:Literate DevOps
by tronbabylove on Sunday August 30, 2020 @12:16PM
(#24323785)
I suspect a mandate to use Org could be counter-productive.
One of Org's unique advantages is the pliability it has by virtue of running in Emacs. I doubt whether someone who was forced to use it would have the intrinsic motivation to climb the notoriously steep learning curves for both Elisp and Emacs. Subtract Elisp (and with it, the ability to do any debugging or customization) and you're left with stock Org mode running in an inferior text-editor.
Maybe stock Org is still enough of an improvement over Markdown that it's worth the overhead of learning Emacs, but I'd have a hard time making that pitch to my coworkers.