I paid for a license on one of the versions. I initially got upset when there was a major release that auto-updated and I got the pop up. However, I looked at my purchase date and it was so many years ago, and I was able to roll back to the version I paid for, so I definitely got my money’s worth. I didn’t end up buying the newer version, because work was forcing me onto VS Code.
That guy is living off that money, and Sublime is one of the best text editors out there. Consider it like a SaaS, but something doesn't break or stop when your license expires.
If you think the price doesn't reflect the value the software brings, then it's your choice, and that's fair. But as for the things it brings to the table, I don't think it's that expensive.
I pay similar for BBEdit, and it saves my bacon regularly. Plus it's dependable.
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.
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 ...”
On the LSP stuff, yes it did originate in VS code. I just find the experience in Sublime to be better. How ironic is that?
I didn't consider the conflict between how I said "try the OG" but then say "VS code is the OG". It is a good point.
I show an example of the block level key binding. So yeah, I needed it and used it. I only showed one example but I have a few more that are my own I just didnt write about them.
Around python vs. js for plugins, have you tried to make a VS code plugin? You need a package.json, npm, and vsce installed globally. Which language is being used is usually the least of my problems. For Sublime, you need a single .py file! Someone shared this 9 line plugin they made: https://gist.github.com/ckunte/31500c17452b0fd8c55bc9460bd9c... - I don't tthink plugin development could be more simple
I bet an LLM could spit out single file plugins very easily. VS code plugins are clearly more work to create and deploy even after taking into account my critiques of Package Control. At the end of the day you can just toss your plugin in a folder or push it to github and reference it with a URL.
I didn't say the docs were "terrible". I just said they were disjointed. They are complete and fully document the APIs. I just wish they were more like the PHP docs or the ones for VS code which are docs plus guides.
All your other points are fine critiques. I'll chalk the other complaints up as a matter of opinion
You’re either hiring developers from countries where $100 is a lot of money, or you expect them to only open Sublime Text once a year. Don’t be stingy—$100 is a steal when it’s the primary tool for nearly every developer. You probably spend that much (or more) on a weekend outing with your partner or friends.
I liked sublime text, but 65$ per year you can get the jet brain ide you need and it already includes most things you need and depends not on plugins from third party.
I'm curious where you're seeing jet brains subscriptions for $65 per year? Only RustRover and WebStorm seem to be somewhat close, with the rest being significantly more expensive.
I often see downvotes when people criticise ST's pricing, but I mostly agree with the detractors - the price always seems to be just a few bucks over the magical limit I'd be willing to pay.
Tech workers often spend $100 or more on a fancy meal with friends in a single night—I've definitely done that more than once. So paying $100 for a software license that I’ll be using almost every hour of the workday, and even more when working on personal projects, feels like a bargain.
I do wonder why it is that way though, because you're right, I've balked at the cost of software before, but had no issue in spending an order of magnitude more money on a flight to SF to meet up with other developers.
probably because there's a free OSS equivalent to most software.
The free equivalent to meeting up with friends/developers is a zoom call, and those suck.
