3 ms·

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 advantag

by 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.