3 ms·

This is a little teaser of some of the more easily demonstrated visual changes in ST4, but we've got a huge collection of new features, tweaks and bug fixes com

by wbond 6y ago

This is a little teaser of some of the more easily demonstrated visual changes in ST4, but we've got a huge collection of new features, tweaks and bug fixes coming. The community is actively maintaining an LSP package, and we've added a number of features in ST4 that the protocol requires, such as UTF-16 diffs.

kamranjon 6y ago
I'm really excited about the new release, thanks for building one of the fastest text editors in the game. I use it every day and couldn't develop without it.
hn8788 6y ago
I love sublime text, but I really wish you'd reconsider relying on a community LSP package. There was an issue a year or two ago where the LSP package couldn't be installed due to a dependency issue in the package, and since it's a community package, they could only fix it when they had enough spare time. I think it was a 1-2 month timeframe where there was no way for new installs to have LSP functionality since it required a third-party plugin.
- wbond 6y ago
  We looked into the protocol, but unfortunately it made a number of poor architectural choices that leads to many language servers not implementing the protocol properly. This effectively requires custom integrations for most language servers. That wouldn't make sense to do in the core of the editor, since we'll never be primary users on the vast majority of servers. The open source model makes sense since it will need to have tweaks and fixes to support various language servers. That combined with a very small development team (six engineers across our two products), would probably lead to slower development, and it would be tied to the release cadence of the main product.
  - hn8788 6y ago
    That makes sense, I didn't know how small the team was. Thanks for the response, looking forward to ST4.
  - modeless 6y ago
    That's unfortunate, but I still think it would be best if you could at least add support for one or two servers in the core, with extensibility for others. Or officially adopt and support the community LSP plugin. My experience with the community LSP plugin has not been good, and it almost led met to switch to vscode. (That and debugging which is a whole other can of worms.) I really think working on LSP would be a better use of your time than continuing to improve the current fuzzy indexing engine.
    - ben-schaaf 6y ago
      The problems you're likely had with the community LSP plugin were due to a lack of APIs provided by ST. For ST4 we've worked together with the community LSP plugin authors to properly support it.

by wbond 6y ago

kamranjon 6y ago

I'm really excited about the new release, thanks for building one of the fastest text editors in the game. I use it every day and couldn't develop without it.

hn8788 6y ago

I love sublime text, but I really wish you'd reconsider relying on a community LSP package. There was an issue a year or two ago where the LSP package couldn't be installed due to a dependency issue in the package, and since it's a community package, they could only fix it when they had enough spare time. I think it was a 1-2 month timeframe where there was no way for new installs to have LSP functionality since it required a third-party plugin.

wbond 6y ago
We looked into the protocol, but unfortunately it made a number of poor architectural choices that leads to many language servers not implementing the protocol properly. This effectively requires custom integrations for most language servers. That wouldn't make sense to do in the core of the editor, since we'll never be primary users on the vast majority of servers. The open source model makes sense since it will need to have tweaks and fixes to support various language servers. That combined with a very small development team (six engineers across our two products), would probably lead to slower development, and it would be tied to the release cadence of the main product.
- hn8788 6y ago
  That makes sense, I didn't know how small the team was. Thanks for the response, looking forward to ST4.
- modeless 6y ago
  That's unfortunate, but I still think it would be best if you could at least add support for one or two servers in the core, with extensibility for others. Or officially adopt and support the community LSP plugin. My experience with the community LSP plugin has not been good, and it almost led met to switch to vscode. (That and debugging which is a whole other can of worms.) I really think working on LSP would be a better use of your time than continuing to improve the current fuzzy indexing engine.
  - ben-schaaf 6y ago
    The problems you're likely had with the community LSP plugin were due to a lack of APIs provided by ST. For ST4 we've worked together with the community LSP plugin authors to properly support it.