8 ms·
The Future of Emacs, Guile, and Emacs Lisp
- JadeNB 12y agoThe headline, which currently appears on HN as "The future of Emacs, Guile, and Emacs", is actually the less redundant "The future of Emacs, Guile, and Emacs Lisp".
- goldfeld 12y agoI see the argument that Emacs Lisp is what we have and works fine floated around by many Emacs veterans, but I wonder if they realize the unrealized potential (opportunity cost) of keeping Guile Scheme out (as Stefan seems to prefer, whereas RMS is in favor of Scheme), and that Emacs going forward can probably yet produce more wealth of extensions than in the past 30 years? I completely agree that keeping full compatibility with all existing extensions is the absolute priority for the new Guile engine, but I myself have kept away from coding anything in Emacs Lisp other than a simple lambda binding because of Elisp's warts and very forgettable ways to do common things (e.g. manipulate strings in general.)
- danohuiginn 12y agoI don't think anybody is proposing to move away from emacs lisp as the usual scripting language. Rather, you'd initially move to Guile's implementation of emacs lisp, and potentially later allow use of other languages supported by Guile.
- Crito 12y agoThis is exactly right. The proposal is to change elisp implementations. elisp the language won't be going anywhere anytime soon.
- cammsaul 12y agoI find http://hyperpolyglot.org/lisp http://hyperpolyglot.org/lisp to be extremely useful for cases when I know what I want to do but don't remember how to do it in Elisp.
- mitchty 12y agoBrilliant, thank you very much!
- vithlani 12y agoAwesome resource.
- ordinary 12y agoA word of warning for Elisp hackers: the Emacs Lisp part of that resource was written by someone with a CL background. I'm seeing various examples that are not conventional Elisp. For instance, ' is used instead of #' for function quoting in various places (prevents compilation of the function) and use of eval on a form instead of apply on a list (dangerous and also prevents compilation of the form). In addition, many of these features use the cl package at runtime, which will cause the compiler to throw a warning, because it's not allowed in Emacs proper. That said, there's a lot of information here that's very useful for the starting Elisp programmer.
- Grue3 12y ago>For instance, ' is used instead of #' for function quoting in various places (prevents compilation of the function) and use of eval on a form instead of apply on a list I don't see how these are evidence of the author having "CL background". CL is pretty much identical to Emacs lisp with regards to both of these things.
- ordinary 12y agoTruth be told, I know nothing of CL. I do know quite a bit about Elisp, and since it's not an Elisp-ism, and the CL and Elisp columns share so much identical code (a lot from cl.el), I assumed it was a CL-ism. My bad.
- PuercoPop 12y agothe #' in CL and Elisp are not the same. Elisp is a lisp-1 vs CL 'lisp-2'. The only similarity is that #'foo expands too (function foo). In CL (function foo) looks up foo in the function namespace (and iiuc can be omitted where functions are expected) in elisp the function form is like quote except for when byte-compiling. It allows the function to be byte-compiled.
- melling 12y agoWow, time sure does fly. I was discussing Guile and Emacs 5 years ago on StackOverFlow. The 10 year old article that I referenced is no longer there. http://stackoverflow.com/questions/1663627/guile-and-emacs http://stackoverflow.com/questions/1663627/guile-and-emacs That's 15 years of talking. My personal feeling is that sometimes it's just better to abandon projects that stagnate. There's an open source Go version of Sublime, for example. It would probably be easier to maintain. https://github.com/limetext/lime https://github.com/limetext/lime
- abroncs 12y agoThat, or contribute to Neovim https://github.com/neovim/neovim https://github.com/neovim/neovim
- scrollaway 12y agoNeovim is a fantastic project, even if you're not interested in vim. They are a model example of how a FOSS kickstarter should be run.
- charlieflowers 12y agoSad to see you were downvoted. It's definitely a legitimate point of view that at least deserves to be brought up.
- TheCondor 12y agoI love emacs and it pains me to agree with this, at least in part. It has reached an odd place, there is enough legacy code (or so it's believed) that it can't be abandoned, there are clear innovations that will never go in to elisp (jit compilation, threads, Ffi, etc) and guile isn't being accepted while it is clearly the best way forward that has been suggested. It's like emacs is done. Considering something else only makes sense...
- easytiger 12y agoAre you living in the real world? The complexities are around keeping a stable platform that some of us have been using for 10-15 years with few complaints. As with any corporate product, you can't go changing shit when you have a large paying userbase.
- deleted 12y ago[deleted]
- pjmlp 12y agoFor me that boat sailed a long time ago, around 2005. Since 1996, Emacs was a kind of IDE replacement when I was in UNIX environments and could not use my beloved MS-DOS/Windows IDEs, but nowadays UNIX systems also enjoy quite powerful IDEs.
- deleted 12y ago[deleted]
- webkike 12y agoEmacs development is going quite incredibly right now. For those unread on the mailing list, here are what I consider to be the most important updates of the past week or two: * 24.4 will be released next Monday (yay!) * Dynamic module support is near completion (or has been completed and awaiting mainline integration). Seriously, Emacs is incredible.
- lmedinas 12y agoSo i know what i have to do! Upgrade all my machines to the new version. September/October/November is definitly the best season of the year. New iOS, Android L, OSX, Ubuntu and of course Emacs :) i hope i'm not missing anything.
- rbanffy 12y agoAt least for Ubuntu, Christmas comes twice every year.
- sdevlin 12y agoWhat are dynamic modules?
- webkike 12y agoDlls essentially. http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries...
- Skinney 12y agoSo... it allows us to download pre-compiled packages?
- arglothy 12y agoIf so, it seems like it might be a big step backward for portability. One of Emacs' big advantages has been that it (and most of it's packages) work on every major desktop operating system. I share a common configuration between Linux and Windows. If this weren't possible I'd probably start looking for a different editor.
- dimitar 12y agoMaybe making the branch a fork will not be that bad for all parties.
- krupan 12y agoI agree. Like the way Xemacs spurred general emacs advancements for a while.
- mahmoudimus 12y agoDoes the Guile team need to raise money? The OP suggests that it "strains the Guile team" and mentions resources many times. Why can't we have a kickstarter campaign for providing funds to develop a real plan of execution for this? Without a real plan forward, I see Guile realistically taking another 5-10 years, making it a 20-25 year long proposal.
- pm215 12y agoI think 'resources' there generally means "engineering resources", ie skilled people, not 'funding'. It's not necessarily easy for an open source project to translate money into engineers. A pot of donated cash in the bank doesn't mean that the existing developers have any more time to work on the project, or that somebody new with the right skills and experience with the codebase magically appears. If one or more project members happen to be consultants who can use the money to spend six months working on Guile rather than on some other paid engagement that's one thing; but the amount of money required to make "quit your full time job to work on the project" financially sensible is prohibitively larger.
- AceJohnny2 12y agoIndeed. I can add that for some projects, funding is useful to acquire the hardware and infrastructure to host the project: code hosting, build servers, test machines, bandwidth... However I doubt this is Guile's constraint.
- mahmoudimus 12y agoI am in complete agreement, in the general sense, with both you and the parent. However, I'm not proposing they hire engineers to work on the bigger pictures of Guile, and as the parent suggests, a "magical codebase" appears. From Eli Zaretskii's own email[1], there are some very low hanging fruit that can be accelerated through funds -- like solving non-GNU compatibility. We can see more tasks at the GuileEmacsTodo[2] list and the various Google Summer of Code sponserships for Guile [3]. These sponsorships have helped Guile make huge gains in the past 4 years. My suggestion is to just keep that momentum going, year around. I know about the mythical man-month, etc, but in this case, some of this low-hanging fruit can be financed. - [1] http://lwn.net/Articles/615347/ http://lwn.net/Articles/615347/ - [2] http://www.emacswiki.org/emacs/GuileEmacsTodo http://www.emacswiki.org/emacs/GuileEmacsTodo - [3] https://www.google-melange.com/gsoc/project/details/google/gsoc2014/bpt/5803402760028160 https://www.google-melange.com/gsoc/project/details/google/g...
- SloopJon 12y agoPrevious discussion of the email thread that prompted this article: https://news.ycombinator.com/item?id=8328206 https://news.ycombinator.com/item?id=8328206
- wtbob 12y ago> Templeton, for example, noted that Common Lisp has no feature that corresponds to Emacs's buffer-local variables, which are often used in Emacs extensions. I don't know about that; it sounds very much like dynamic variables. It's usual in a Common Lisp implementation to give each thread its own set of dynamic variables (indeed, that's close to the only sane thing to do); I can't offhand see why it would make sense just to treat buffer-local variables similarly. But perhaps there're some semantics I'm not familiar with.