Re:De-Bloated Windows 11 Build Runs on 2GB of RAM
by MuffinFlavored on Saturday February 04, 2023 @11:35AM
(#34655665)
Isn't it interesting that both you and I frequently use Sublime and VS Code? Why can't VS Code kill off Sublime? It's interesting to me where a text editor like Sublime can't be a preferable IDE, but an IDE also isn't a preferable text editor?
[ Parent
| on HN ]
Re:De-Bloated Windows 11 Build Runs on 2GB of RAM
by speg on Saturday February 04, 2023 @12:22PM
(#34656140)
Sublime is, well, Sublime.
Every time I try VS Code I just can’t commit. There’s a bit too much going on and it never feels as tight as Sublime.
I did just get a new Windows machine, so maybe I should try it on that.
Re:De-Bloated Windows 11 Build Runs on 2GB of RAM
by MuffinFlavored on Saturday February 04, 2023 @12:34PM
(#34656267)
When you are using Sublime, do you have the ability to right click somewhere and "go to definition" in a big code base?
Re:De-Bloated Windows 11 Build Runs on 2GB of RAM
by nickpeterson on Saturday February 04, 2023 @08:44PM
(#34660731)
I have the same feelings. Sublime has really good, “let me visually manipulate text through cursors” functionality. The find all, regex highlighting, and multi cursors are really nice. These features are in nearly every editor but they always feel crappy to use compared to sublime.
I’m starting to get back into emacs recently though because I like fiddling with tools more than productivity.
Re:De-Bloated Windows 11 Build Runs on 2GB of RAM
by tkuraku on Sunday February 05, 2023 @12:01AM
(#34662076)
I've migrated to vscode from sublime. Vscode integrated debugger, lsp, etc are way ahead of sublime. That said, typing in sublime just feels good compared to vscode. I keep sublime around for quick edits.