24 ms·
The only thing holding me back from experimenting with org-mode is its tight coupling with emacs. It's a non-starter on a team where people aren't willing to s
by smallnamespace 8y ago
The only thing holding me back from experimenting with org-mode is its tight coupling with emacs.
It's a non-starter on a team where people aren't willing to switch over to it (at least to view and interact with org files).
It's difficult for anyone who has a heavy reliance on IDE features; I've spent literally probably close to a hundred hours trying to get emacs + IDE-like integrations working for a variety of languages, with only mixed success.
Yes, I understand that going with emacs is a 'different way' of doing things, and perhaps you won't need your IDE if you just do things the emacs way, but the barrier to entry is very high, between building in new muscle memory for shortcuts, the highly non-standard UX compared to every other editor today, and the hours and hours required to configure everything by hand, even with a starter config like spacemacs.
- stevesimmons 8y ago> The only thing holding me back from experimenting with org-mode is its tight coupling with emacs. As a non-emacs user, my successful route to orgmode was with Spacemacs and evil for Vim keybindings. After several false starts, what worked for me was: 1) realizing I didn't need to go full emacs: I stick with Vim for plain text editing, Visual Studio for coding at work and PyCharm/Visual Studio Code for coding at home. 2) consciously learning one new org-mode feature at a time, and adding their shortcuts to my own cheat sheet.