2 ms·
OP isn't much but a 'emacs is successful despite being bad software engineering in these ways', which isn't all that interesting. What would be more interesting
by gwern 16y ago
OP isn't much but a 'emacs is successful despite being bad software engineering in these ways', which isn't all that interesting. What would be more interesting is a discussion why those ways aren't bad for emacs or how emacs overcomes those handicaps.
For example, in an earlier Cook post on Unix philosophy, I linked http://www.johndcook.com/blog/2010/06/30/where-the-unix-philosophy-breaks-down/#comment-71525 http://www.johndcook.com/blog/2010/06/30/where-the-unix-phil... to ESR's discussion of Emacs http://www.catb.org/~esr/writings/taoup/html/ch13s03.html#id2967765 http://www.catb.org/~esr/writings/taoup/html/ch13s03.html#id... and the followup discussion about the interesting idea of contexts/frameworks http://www.catb.org/~esr/writings/taoup/html/ch13s04.html http://www.catb.org/~esr/writings/taoup/html/ch13s04.html
That could be more than a blog post, it could be a real contribution.
- ColinWright 16y agoBut even though the OP doesn't have that, I was hoping the discussion here could, in effect, "crowd-source" such a contribution. So often in the past on HN I've seen relatively content-poor posts lead to serious discussions that pull together expertise and experience from a wide range of people, and the discussion has been a great reference. EDIT: Don't mind the down-vote(s) - don't really care about karma - but I'd love to know why people disagree with my comment. Thx in advance.