![]() ![]() Having fantastic graphing capabilities and embedding of graphic tools such that the work flow can exploit both graphics manipulations and text operations would be a huge boost in capabilities, something which adding to Emacs would be much harder due to so much legacy code in the platform that will have to be accommodated in the process.Īs an example, people have really wanted to move Emacs underlying language from elisp to common lisp for a long time, but it is such a massive undertaking and transitioning the community to using it would be so difficult that (without a team to work on it constantly) no one has succeeded in doing so fully. That is a thought that really resonates with me. His point in one presentation that while Emacs and VIM are fantastic at text related operations, there doesn't exist something comparable that has both great support for text and great support for visualization. If that happens I think I will make a lot of effort to bring it up to speed with features Emacs has but Light Table doesn't at the time.Ĭhris Granger has made a lot of smart design decisions that really appeal to me about Light Table. I am hoping that Light Table is released with a license and degree of openness that provides a similar degree of hackability as the Emacs platform does. So, a new iteration of Emacs would require a very free license for me to have confidence that my efforts won't be wasted in a short period later. Proprietary programs are a deal breaker for me as far as contributing to them in my free time a great deal due to how frequent they go out of business and lose support. I am hoping either that occurs or there exists a viable replacement for Emacs that incorporates the improvements more easily due to starting with a blank slate. It would be a lot of work to do and doing so requires a set of skills that are much less available than other software engineering skills unfortunately. So yeah, could someone get on that please? Thanks :)Įmacs could gain a lot of performance boosts with some significant changes to its architecture. Oh, and also, unlike every modern day attempt at an editor, it should still support running in a terminal, because terminals are still damn useful. Think maybe replace elisp with LuaJIT, and take cultural inspiration from the make-it-fast ethos of git and the make-it-correct ethos of sqlite. Emacs is a giant ball of elisp mud that's perpetually half-broken, half-implemented, or slow.but it's still the best thing going, by more flexible and more useful than any other editor out there (AFAIK).īut I'm not convinced it isn't possible to do something as flexible as emacs without all the random breakage and general lack of concern for performance. ![]() See that sleep-for? That's an awesome built 1-second pause while waiting, for example, for an emacs shell to startup if you have a custom. but has bad results if the comint does not prompt at all Or check out this awesome, high-performance code from the function comint-exec: The python-people python mode doesn't lock up, but narrow-to-defun takes maybe 300ms (not terrible, but clunky feeling way worse than instant), for some reason. Rather than track it down, I went back to using the latest python-people python mode (for some reason, the emacs people insist on writing their own python mode, rather than using the one the python people wrote). The latest emacs python mode for some unknown reason would freeze for like 10 seconds when opening certain python files. After the suffering got high enough, I finally tracked down how to revert to the old behavior. Moreover, it completely locked up emacs while doing the search (since emacs is single-threaded and synchronous). A recent version of emacs changed the default shell history command to show live search results (like bash does), but the emacs implementation was ungodly slow if your bash history was longer than a few dozen items (waaay slower than a real terminal interactive bash search). To give a couple examples off the top of my head: ![]() I'm not so sure people keep adding stuff to emacs, and performance doesn't really seem to be a priority. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |