3 ms·
I'm blown away by how snappy this is. It always is, but it's even better now. This is really impressive work. I don't think I'm the target audience here. I jus
by steve_adams_86 5y ago
I'm blown away by how snappy this is. It always is, but it's even better now. This is really impressive work.
I don't think I'm the target audience here. I just spent 30m trying to tune this for a TypeScript project, and I can't seem to easily get eslint, prettier, and a few other tools working. I added the TypeScript language server package, but it doesn't offer any of the effortless reference navigation and refactoring I'm used to.
Having said that, am I just missing something? Can Sublime be that kind of editor?
I think I'd love to give it a shot, but without these conveniences I'm feeling like I should stick with VS Code.
- xputer 5y agoI use Sublime instead of vim/gedit/notepad/notepad++ for quickly viewing files. The main benefit of Sublime over VSCode is that it opens several orders of magnitude faster. However, in terms of doing actual programming work I prefer VSCode over Sublime because it has way better plugins.
- schneidmaster 5y agoI've used the following list of packages for eslint, prettier, and TypeScript. It's not as effortless as it should be, but the two LSP packages in particular do give reference navigation that's pretty equivalent to VS Code. - https://packagecontrol.io/packages/SublimeLinter https://packagecontrol.io/packages/SublimeLinter - https://packagecontrol.io/packages/SublimeLinter-eslint https://packagecontrol.io/packages/SublimeLinter-eslint - https://packagecontrol.io/packages/JsPrettier https://packagecontrol.io/packages/JsPrettier - https://packagecontrol.io/packages/LSP https://packagecontrol.io/packages/LSP - https://packagecontrol.io/packages/LSP-typescript https://packagecontrol.io/packages/LSP-typescript If you're on macos, I also recommend creating a file at ~/Library/Application Support/Sublime Text 3/Packages/User/Default (OSX).sublime-mousemap with the following contents -- this adds a cmd+click "go to definition" shortcut that's also equivalent to what VS Code provides. (I guess the path should be "Sublime Text 4" now? but after upgrading, the config at the "Sublime Text 3" path still works for me.) [ { "button": "button1", "count": 1, "modifiers": ["super"], "press_command": "drag_select", "command": "lsp_symbol_definition" } ] I've tried to switch to VS Code a few times -- language features (especially TypeScript) tend to work better out-of-the-box but it still isn't close in terms of performance. If you want IDE-like features to "just work" then VS Code is definitely the best choice, but the persistent (albeit sleight) input lag drives me up the wall.
- merryMellody 5y agoThank you so much for this! I was looking for an optimal config myself, and this saved me so much time :-) Cheers!
- e_proxus 5y agoSublime can definitely be that kind of editor, but requires quite a lot of setup in some cases. There is a language server plug-in, which (IMO) is not straight forward to customize or even setup, with very little feedback when something goes wrong (broken LS implementation, or misconfiguration). However, when it does finally work, it's super snappy and clean. The philosophy of Sublime is almost opposite to VS Code and other IDEs. Instead of everything enabled by default, everything is simple and lightweight by default. Then you add your own things on top. I mostly see it as analogous to programming, where I too prefer to start simple and add things I control on top and where I understand the whole stack. Compared to picking a huge framework which lets me get started but where I don't understand the hundreds of layers beneath. Since I use Sublime Text since years, and plan to use it for years to come, I see it as an investment to learn the underlaying functionality and eco system from the ground up. It makes me a better and more productive programmer in the long run.
- laurent123456 5y agoSublime Text used to be my main editor but when I've started developing more in TypeScript I dropped it because I could never get it working well enough. I'm using VSCode now and TypeScript with it just works without having to install and configure many half-working packages, some of which will conflict with other packages you might use. Perhaps ST4 addresses these issues, but personally I probably won't go back to it.