I used to be a big Emacs user, especially in my postgraduate days and would love to go back to the run everything in Emacs days but the world has changed. These days I only use it for editing text.
The many problem is that Emacs hasn't really kept up with the times. It's bloated in the wrong ways with too many default packages installed. Asynchronous processes and integrating WebKit to allow binary buffers (PDF, Images, SVG) would solve a lot of issues but I can't see it happening without a fork given the stubbornness of RMS. The recent spat over AST in gcc (which would again improve Emacs) doesn't increase the hope that things will change anytime soon.
And that the sad thing. The idea of Emacs, a scriptable, extensible environment is timeless and should not be lost to the past.
(BTW I would pay money for an Emacs fork and modernization project)
Jamie Zawinski later went to work at Netscape where he was responsible for the Unix version, and named the Mozilla open-source project that you have heard of. He cashed out of Netscape and bought the DNA Lounge nightclub.
On his blog, he likes to point out software inanities with the caption "This is why I sell beer now")
The many problem is that Emacs hasn't really kept up with the times. It's bloated in the wrong ways with too many default packages installed. Asynchronous processes and integrating WebKit to allow binary buffers (PDF, Images, SVG) would solve a lot of issues but I can't see it happening without a fork given the stubbornness of RMS. The recent spat over AST in gcc (which would again improve Emacs) doesn't increase the hope that things will change anytime soon.
And that the sad thing. The idea of Emacs, a scriptable, extensible environment is timeless and should not be lost to the past.
(BTW I would pay money for an Emacs fork and modernization project)