zlacker

>>james2+(OP)
Sublime Text is so awesome, I don't mind it's constant begging for a license purchase or whatever. It's right up there with Winrar.

>>notepa+p1
And the license is awfully expensive. I was going to the website to pay $50 for my 7 developers, but it turns out it’s $100. No way.

Or $65 per year: https://www.sublimehq.com/store/text

>>eastbo+F1
I think Sublime Text was the first software I ever paid for. It has paid that back handsomely. And no, I’m not doing the usual “I’m a working professional so my time is directly attributable to my text editor” thing. I understand there are free options. I pay for it despite there being competition because of the extra value it brings me.

>>saagar+x2
What extra value does it bring you compared to free alternatives like Notepad++?

>>noname+M6
Not trying to be rude but the article does a pretty good job laying out some reasons why I pick it.

>>saagar+07
I was interested in the value that it brings you. I'm a former Sublime Text user and I switched to VS Code some time ago.

Do you also use Sublime Text as your primary IDE just like author does?

————

Mirroring the structure of the article:

1) Regarding the section about LSPs: do you also have the need to be able to “just add an LSP installed as a binary in on your usr/local/bin” even though by the author's own admission “VS Code is the LSP king”?

Kind of ironic to have the author say in the introduction about VS Code that “it probably has taken inspiration from Sublime. So why not check out one of the OGs” and then a bit later proceeds to say that the LSP “tech originat[es] with that editor [VS Code]”. I'm returning the question to the author and you: why not check out the OG?

2) Regarding the section about snippets author says that “VS Code can do this” and even that “the syntax for it is a bit nicer”.

3) Regarding workspaces VS Code does all of that. Author admits that he “ha[s]n't used it personally, so [he] can't speak to it much”.

4) Regarding build systems VS Code does all of that and it's easier because contrary to “the Package Control [that] is not part of Sublime” (and that you have to uglily inject in the Sublime Text console to get working), the VS Code plugin repository has everything already ready-to-use so that you don't need to reinvent the wheel. You can if you want though; Sublime Text doesn't provide anything extra in that regard.

5) Regarding the “Multiple cursors” VS Code has it as well.

6) Regarding the block-level key bindings, have you ever needed them? For me the last thing I want is for my shortcuts to change dynamically based on which block I am in the file. Note that in Sublime Text “they cannot be saved on a per-project basis”, which is awkward to say the least. I would (much) rather have project-level keybindings rather than only block-level keybindings that apply globally.

7) Regarding using “Python all the way down” rather than JavaScript, I'm surprised that the author finds it to be a good thing considering that they primarily use it for “web-dev” and all their examples are frontend Javascript code.

8) Finally, the author complains about the terrible documentation of Sublime Text, the lack of a plugin system, and the fact that for the 3rd-party hacked-together plugin management system he finds that getting them on the “Package Control site to be quite a chore”. I have a ton more complaints about Sublime Text to add on top of that.

I would rather directly donate money[1] to small developers rather than — as another commenter puts it — “supporting and using the products developed by a small team of dedicated engineers ...”

————

[1] And I do! Currently sponsoring 14 developers on a monthly basis[1]: https://github.com/devnoname120?tab=sponsoring