4 ms·
I'm torn. On the one hand, I definitely want emacs to be faster as it does more and more for me. However, I also want more and more of the things that folks a
by taeric 9y ago
I'm torn. On the one hand, I definitely want emacs to be faster as it does more and more for me. However, I also want more and more of the things that folks are doing in emacs to be driven by other processes. Preferrably ones I can use outside of emacs to get answers.
As an example, I get that emacs would have to parse the entire buffer I'm in in order to syntax highlight as I'm typing. For that, I think this is going to be required. However, emacs should be able to offload to another process to look up external symbols. GLOBAL is the tool I use nowdays, and updating the tags database or looking up symbols is something that should be getting heavy lifting in an external process.
Or am I looking at things the wrong way?
- gkya 9y agoIIRC tags databases are big files that need to be parsed and operated on via Elisp, so a faster interpreter would be beneficial there. I don't think a faster interpreter would hinder integration of external tools, given often they do not only provide speed, but also quality software with proven longevity.
- taeric 9y agoTraditional ones, yes. However, modern tag databases are just that, databases. Sending a query to a database to find all callers and such can be offloaded to another process easily enough. Note that this isn't really that new, for the modern tag. Cscope was already an external command. And you already offloaded the tag creation to an external process. I see very little need for the tag navigation to all be in elisp. The final selection, of course, can still be in elisp. Since that will be user input driven.
- gkya 9y agoEmacs now has C extension support, which might be helpful in fast interactions with external tools too.
- sedachv 9y ago> GLOBAL is the tool I use nowdays, and updating the tags database or looking up symbols is something that should be getting heavy lifting in an external process. What do you use for GLOBAL? ggtags.el works like you describe (calls start-file-process to start a GLOBAL process).
- taeric 9y agoApologies, I meant that to be an example of how I think it should be. Not a hypothetical, either. Like you say, you can already write things this way. My only complaint is it still blocks sometimes. Overall, works like a champ.
- xfer 9y agoThis is the area that lsp in general is trying to address. Most of the problems with elisp isn't its speed, imo.
- eadmund 9y ago> However, I also want more and more of the things that folks are doing in emacs to be driven by other processes. Preferrably ones I can use outside of emacs to get answers. … there's life outside of emacs? grin I'd rather do stuff in-process, but with good support for asynchronicity. It's nice that I can M-. to the definition of anything I'm using, nice that I can patch it in-memory and nice that it's all written in a decent language (elisp isn't perfect, but it's pretty good).
- barrkel 9y agoI agree. I think language servers are the way to go, ideally leveraging the same lexer and parser as a production compiler / interpreter to avoid mismatches.
- taeric 9y agoI'm also torn on that idea. I think multiple parsers and such are healthy for the ecosystem. Mainly because I am heavily swayed by the dangers of monocultures. So, to that end, I think it is healthy that there are at least 3 powerful javascript implementations. I just wish there was more equalization in the marketplace for them. And, I cannot argue against the merits of a language server. Having a single one would be more efficient in many ways. I just find our fixation on "not reinventing the wheel" to be detrimental in many ways. I'd rather we were "don't get stuck with a monoculture." And I say this as someone that highly respects the LISP community. It is impressive how much you can do with really old libraries there.