4 ms·

> Lime Text is a powerful and elegant text editor primarily developed in Go It's very interesting to me that this is the most important statement the creators

> Lime Text is a powerful and elegant text editor primarily developed in Go It's very interesting to me that this is the most important statement the creators can make about their project. Of course anyone making a text editor will say it is powerful and elegant. As an end-user, I rarely care what language a text editor is written in. At least not right up front. It might matter if I'm interested in extending or modifying it. Maybe this fragment can be improved. The second half of the sentence actually gives me an idea what problem it is solving and why it exists: > that aims to be a Free and open-source software successor to Sublime Text. (Awesome!) The second paragraph is also very interesting and draws my interest. I love the "Roadmap" button, neat touch. It shows very clear goals and a reasonable amount of progress.

flukus 10y ago
I also want to know why it's better than the myriad of other text editors out there. Evaluating a text editor and it's extensibility is a time consuming task.
matmann2001 10y ago
For the people they are targeting by calling it a successor to Sublime, the language actually does matter. Many, likely most, Sublime users are taking advantage of the myriad of plugins written for Sublime in Python. I immediately discounted the usefulness of this product simply because it is written in Go, which would mean I need to find new equivalents for the plugins I use on a day to day basis, or write Go versions of them myself. I honestly don't have enough to complain about with Sublime that would make switching worth that amount of effort.
- Arcsech 10y ago
  For what it's worth, it does aim to be (mostly) compatible with the Sublime Text Python API[0]. The base editor is written in Go, but the plugins are Python (much like Sublime itself is C++, but uses Python plugins). That said, I wouldn't get too excited about this - not much has really happened on it since April 2015. [0]: It's the fifth point on the roadmap: https://github.com/limetext/lime/wiki/Goals https://github.com/limetext/lime/wiki/Goals
- pkroll 10y ago
  That's understandable, but maddening. Why are scripts that control/operate with an editor limited to the particular choice of the editor? Back in the Amiga days, useful things had an ARexx port, and while that meant most scripting was done in ARexx itself anything could send commands and get information back via those ports. You could write scripts in assembler, BASIC, or whatever variant language you wanted.

flukus 10y ago

I also want to know why it's better than the myriad of other text editors out there. Evaluating a text editor and it's extensibility is a time consuming task.

matmann2001 10y ago

For the people they are targeting by calling it a successor to Sublime, the language actually does matter. Many, likely most, Sublime users are taking advantage of the myriad of plugins written for Sublime in Python. I immediately discounted the usefulness of this product simply because it is written in Go, which would mean I need to find new equivalents for the plugins I use on a day to day basis, or write Go versions of them myself. I honestly don't have enough to complain about with Sublime that would make switching worth that amount of effort.

Arcsech 10y ago
For what it's worth, it does aim to be (mostly) compatible with the Sublime Text Python API[0]. The base editor is written in Go, but the plugins are Python (much like Sublime itself is C++, but uses Python plugins). That said, I wouldn't get too excited about this - not much has really happened on it since April 2015. [0]: It's the fifth point on the roadmap: https://github.com/limetext/lime/wiki/Goals https://github.com/limetext/lime/wiki/Goals
pkroll 10y ago
That's understandable, but maddening. Why are scripts that control/operate with an editor limited to the particular choice of the editor? Back in the Amiga days, useful things had an ARexx port, and while that meant most scripting was done in ARexx itself anything could send commands and get information back via those ports. You could write scripts in assembler, BASIC, or whatever variant language you wanted.