3 ms·
I'm not a lisp programmer, but I have used emacs in the past. For people w/ lisp dev XP, can I ask this: Is the ".emacs/config bankruptcy" issue a general prob
by Chris2048 6y ago
I'm not a lisp programmer, but I have used emacs in the past.
For people w/ lisp dev XP, can I ask this: Is the ".emacs/config bankruptcy" issue a general problem? Specifically, when you use so many powerful devices, macros etc; but with little predictable code structure, then further development that sits well with existing code becomes pretty difficult.
- ssivark 6y agoI’m not an experienced lisp programmer, but Emacs bankruptcy is imho avoidable. You must understand that people often configure their editors by the worst of Stackoverflow-driven coding... copy-pasting random snippets till things work, and accumulating cruft over time. Also, Emacs lisp is not particularly great (compared to other lisps) and Emacs configuration is typically done through a bunch of exposed global variables. YMMV. A production codebase hopefully merits very different attitudes :-)
- mijoharas 6y agoAlso, frameworks seek to claw back some structure from the morasses. It's kinda fine if every library you use is _slightly_ different if you can have a unified interface for how to use them (spacemacs layers system for me). It is annoying figuring out which invocation of variables sets the tab-width for _this_ new language though... Also, most libraries in the emacs ecosystem have become more standardised in their interfaces, so things aren't too different nowadays.
- Chris2048 6y agoI think this is the problem. copy-paste a powerful snippet anywhere, no need to put it in a particular place or integrate it into an existing structure. But the global variable thing is interesting; Does regular lisp differ a lot wrt snippets having broad, global effects?