The headline changes in this release are related to the Python plugin host:
- Upgraded Python 3.8 to Python 3.14
- Python 3.3 is now disabled by default
By default, Sublime plugins now all run under the Python 3.14. The 3.8 plugin host was removed (Python 3.8 reached EOL in Oct 2024), and the 3.3 plugin host is deprecated, and will be removed in a future release.
This is great for plugin devs. They get improvements to syntax, performance, type hints, the standard library, etc, and they can depend on modern versions of Python packages. Many packages no longer receive updates for 3.8 (e.g. https://github.com/psf/requests), let alone 3.3, and many others simply don't run on these older python versions (e.g. https://github.com/xberg-io/tree-sitter-language-pack).
Like the plugin systems for Emacs/Neovim/VS Code (and unlike the sandboxed systems for e.g. Zed and Helix), Sublime's plugin API has low-level access to the editor, and the runtime has full OS access.
I think Sublime was smart to bet on Python for the plugin system. They released the plugin system in 2009, before Python was everywhere. The super flexible plugin API and the huge package ecosystem is a powerful combo.
If anyone is following along in the forums and understands the health of the team behind the product, could you give us a read on the prospective longterm health of the product? Most in my circle thing ST is dead or abandoned.
Not very much following the forums, but the pace they are producing things is fine. What is "basic usability thing" for you, might be something unimportant for the rest. How the team sets the priorities might be just fine for a lot of users..
Does ST support opening a repo on a remote server? The last time I used it was back in my freshman year of college, and I haven't touched it since. Does anyone happen to know?
Zed pretty much copied everything over from Sublime, so it's pretty much on par.
Sublime was one of the first editors to have an uncluttered UI without toolbars, but with advanced features, like multi-cursor editing and the command palette.
As a long time sublime users, it still feels superior as it gets lots of small details right, like for example when I do Cmd+P to search for files and scroll through the files it will show a preview, Zed doesn't show a preview until you actually select the file.
Yup, I used TextMate a lot back in the early 2000s, and Sublime from around 2010 and bought a license maybe a year later.
To this day I always install Sublime on my new machines, it's the perfect text editor for my needs: fast and snappy, buffers are persistent so I can use as a scratch pad without having to save files, can customise with plugins if needed, the command palette gives quite a bit of power user features.
I mostly use it as a scratch pad nowadays, like if I'm debugging something, collecting a bunch of text from different places to reference quickly, nothing too advanced (nor directly related to coding) and is still one of the most satisfying programs to use on my day-to-day. It's basically always open, just waiting for a new buffer.
Technically correct. However, for the majority of humans, their first encounter with these features and behaviors could never be TextMate, and instead would be Sublime Text. TextMate never growing to be cross-platform is a major reason for Sublime Text's early growth.
I use Sublime mostly these days but I still have a soft spot for TextMate. Sublime is the closest that exists to its spiritual successor, but it’s missing the “macness” that TextMate brought back in the day, which is the cost of being a cross-platform app I suppose.
Sublime text is what notepad++ wished to be. There are many tasks that do not require a full IDE, not even vscode and sublime just works. Always, consistently, reliably works, is fast and a joy to use.
- Upgraded Python 3.8 to Python 3.14
- Python 3.3 is now disabled by default
By default, Sublime plugins now all run under the Python 3.14. The 3.8 plugin host was removed (Python 3.8 reached EOL in Oct 2024), and the 3.3 plugin host is deprecated, and will be removed in a future release.
This is great for plugin devs. They get improvements to syntax, performance, type hints, the standard library, etc, and they can depend on modern versions of Python packages. Many packages no longer receive updates for 3.8 (e.g. https://github.com/psf/requests), let alone 3.3, and many others simply don't run on these older python versions (e.g. https://github.com/xberg-io/tree-sitter-language-pack).
Like the plugin systems for Emacs/Neovim/VS Code (and unlike the sandboxed systems for e.g. Zed and Helix), Sublime's plugin API has low-level access to the editor, and the runtime has full OS access.
I think Sublime was smart to bet on Python for the plugin system. They released the plugin system in 2009, before Python was everywhere. The super flexible plugin API and the huge package ecosystem is a powerful combo.
If anyone is following along in the forums and understands the health of the team behind the product, could you give us a read on the prospective longterm health of the product? Most in my circle thing ST is dead or abandoned.
https://github.com/sublimehq/sublime_text/issues/5984 :)
To this day I always install Sublime on my new machines, it's the perfect text editor for my needs: fast and snappy, buffers are persistent so I can use as a scratch pad without having to save files, can customise with plugins if needed, the command palette gives quite a bit of power user features.
I mostly use it as a scratch pad nowadays, like if I'm debugging something, collecting a bunch of text from different places to reference quickly, nothing too advanced (nor directly related to coding) and is still one of the most satisfying programs to use on my day-to-day. It's basically always open, just waiting for a new buffer.
And whatever it does, it does better than Zed, debatably.