Re:Clarifying some things about Guile-Emacs
by lake99 on Saturday September 20, 2014 @08:15AM
(#8344333)
When I write command-line programs, the JVM seems just fine. Even the startup time is not bad. However, when I compare actual editors and IDEs, JVM-based editors feel as painful as pulling teeth. Compare jEdit and Kate, or even Sublime Text. Or compare Eclipse, IntelliJ, Netbeans, etc. with any native app. Sure, these IDEs do a lot, but when I'm editing some UML diagram in Eclipse, for example, just clicking on an element to see its properties takes a few seconds. Seems like Eclipse is using all its libraries to accomplish this. I'm not running these on netbooks. I am comparing speeds across fairly well-endowed laptops and desktops. Maybe the fault lies not with JVM, but with the rest of the Java ecosystem.
Re:Clarifying some things about Guile-Emacs
by technomancy on Friday September 19, 2014 @12:41PM
(#8341232)
The main performance problems are load time and ARM performance. But moving a flagship GNU project to a runtime with serious patent encumbrance is clearly never going to happen.
I'm not arguing that Emacs should target the JVM but don't see how building it on yet another bytecode VM is going to fix any performance problems.