3 ms·
The problem with org mode (and magit to a somewhat less degree) is that it is tied to emacs. It will never be adopted by 99% of the developer community (or writ
by __mharrison__ 2y ago
The problem with org mode (and magit to a somewhat less degree) is that it is tied to emacs. It will never be adopted by 99% of the developer community (or writing community at large).
I say this as an emacs user who uses org for my company notes.
- mkesper 2y agoAnd I think a lot of it is because of defaults. Whenever I open an emacs without my usual configuration of doom-emacs I have to admit it looks dated. Add to that default keyboard shortcuts not working and you've alienated practically everyone taking a look at it.
- subsection1h 2y ago> I have to admit it looks dated. I assume this is because most Emacs users, especially Emacs devs, disable the menu bar, tool bar, tab bar, scroll bar, etc. > default keyboard shortcuts not working Yeah, I think a new Emacs installation should prompt the user to choose between something like "Common keyboard shortcuts" and "Classic Emacs shortcuts". It would take me only a few minutes to set up all the common keyboard shortcuts for a new Emacs installation, but I think it should be just one setting.
- BeetleB 2y ago> It will never be adopted by 99% of the developer community (or writing community at large). Something that will never be adopted by 99% of folks is totally fine. Most of my SW has less than 1% the adoption of org mode users (and thus less than 99.99% of the dev community will use it). Should I be concerned? Of course not!
- mplanchard 2y agoI keep dreaming about writing a standalone org-mode app, but given how much of people's workflows are likely to be deeply tied to custom elisp that calls stuff from emacs' library or other emacs packages, it seems like a fool's errand.