40 ms·

Atom did this with the backing of a very well-financed company, and it still doesn't fare all that well with niche languages. I agree with the general gist of

Atom did this with the backing of a very well-financed company, and it still doesn't fare all that well with niche languages. I agree with the general gist of your first post, but I think it's important to recognize that unless you can build on some portable standard method for defining editor support for programming languages, there is going to be a cost to living in the niche; it is going to make you more hesitant to experiment with new languages. (This is speaking as someone who has also implemented their own Lua-based text editor.)

sdegutis 10y ago
Oh hey Phil. Didn't see you there. Sure, Atom has Github paying for it, and they still don't have CIDER. But you know what? Emacs users came up with CIDER from scratch. It barely builds on top of any existing Emacs plugins. That exact same thing could have been done in an editor like kilo if it had the right scriptable foundation.
- gkya 10y ago
  But why did they not build CIDER on Hemlock with Common Lisp available instead of Emacs Lisp? Because you need more than possibilites to get working without wasting time. Apart from plugins, Emacs has the core environment to build such a thing, and then there are many libraries that pile up in creating the plugins, that others wrote, so that you don't need to implement a networking library and a string processing library and a syntax definition library and subprocess management library and whatnot in order to build sth. like CIDER. Not that that's impossible, but certainly a waste of time when the tech and the community is already there. It's of course on one's self to choose whether to spend that time or not, and it's not bad or stupid to choose to create one's own editor, but it's undebatable that some time that instead could've been used productively for something else is spent duplicating others' effort, if a brand new idea is not being implemented.
- technomancy 10y ago
  Emacs users came up with Cider, but they were able to do it because there were a whole ton of them. Cider has had 154 contributors: https://github.com/clojure-emacs/cider/graphs/contributors https://github.com/clojure-emacs/cider/graphs/contributors

sdegutis 10y ago

Oh hey Phil. Didn't see you there. Sure, Atom has Github paying for it, and they still don't have CIDER. But you know what? Emacs users came up with CIDER from scratch. It barely builds on top of any existing Emacs plugins. That exact same thing could have been done in an editor like kilo if it had the right scriptable foundation.

gkya 10y ago
But why did they not build CIDER on Hemlock with Common Lisp available instead of Emacs Lisp? Because you need more than possibilites to get working without wasting time. Apart from plugins, Emacs has the core environment to build such a thing, and then there are many libraries that pile up in creating the plugins, that others wrote, so that you don't need to implement a networking library and a string processing library and a syntax definition library and subprocess management library and whatnot in order to build sth. like CIDER. Not that that's impossible, but certainly a waste of time when the tech and the community is already there. It's of course on one's self to choose whether to spend that time or not, and it's not bad or stupid to choose to create one's own editor, but it's undebatable that some time that instead could've been used productively for something else is spent duplicating others' effort, if a brand new idea is not being implemented.
technomancy 10y ago
Emacs users came up with Cider, but they were able to do it because there were a whole ton of them. Cider has had 154 contributors: https://github.com/clojure-emacs/cider/graphs/contributors https://github.com/clojure-emacs/cider/graphs/contributors