I also started using sublime Merge recently and I think I may feel the same way about it
Sublime Text 4 (Build 4126)
21–30 of 110 posts
Re: Sublime Text 4 (Build 4126)
#22Is there any kind of remote development support (ssh, docker) in Sublime? That’s the killer feature that keeps me on VS Code.
Re: Sublime Text 4 (Build 4126)
#23I still daily drive Sublime. I haven’t found an editor with less latency. It’s so fast and so consistent. VS Code feels like Eclipse in comparison.
Re: Sublime Text 4 (Build 4126)
#24I still daily drive Sublime. I haven’t found an editor with less latency. It’s so fast and so consistent. VS Code feels like Eclipse in comparison.
Daily driving to do what type of work exactly? I've been using VS Code for years now, and while it is measurably slower (I still use sublime to handle ad-hoc grepping log files as code just won't handle that, and scrollable, highlighting and multicursor is MUCH better than smacking bash pipes together), the batteries included "It just works" approach of code means I don't really see a reason to head back. Maybe it's…
Re: Sublime Text 4 (Build 4126)
#25I still daily drive Sublime. I haven’t found an editor with less latency. It’s so fast and so consistent. VS Code feels like Eclipse in comparison.
Daily driving to do what type of work exactly? I've been using VS Code for years now, and while it is measurably slower (I still use sublime to handle ad-hoc grepping log files as code just won't handle that, and scrollable, highlighting and multicursor is MUCH better than smacking bash pipes together), the batteries included "It just works" approach of code means I don't really see a reason to head back. Maybe it's…
The packages ecosystem is fine and always has been.
Re: Sublime Text 4 (Build 4126)
#26maybe out of nostalgia, I always have Sublime installed on my computer. nowadays if i need a draft for a copy/paste or need to annotate something fast I use Sublime, which is always running. it became something like my advanced notepad
VSCode is excellent, but I don't think that I do enough of the kind of coding that VSCode is optimized for, to make it worth it.
Re: Sublime Text 4 (Build 4126)
#27Even though I haven't met a Sublime user in a few years, it still must be popular since it's at v4. Last time I checked, Sublime was still proprietary, which is the reason I had skipped using it. I've heard Sublime has some useful features, though. If it's in their interest, I hope they decide liberate / open their source code. E: misspelling
As one of the people supporting it’s continuing existence, I think there will be more focus on what I need. For open source projects, the focus will be (and should be) on what the people putting in the time and money need.
There’s considerable overhead (in terms of optimizing workflows) to switching editors too, so just because an editor is good for today doesn’t mean it will be good tomorrow. Not that proprietary editors can’t change in a way negative for me. I just figure it’s less likely and, over time, will happen less often.
Of course, I could have the perfect editor by doing my own, but it’s orders of magnitudes less effort to pay someone $x. (Personally, I think sublime should go to a subscription model. Pay per release encourages feature bloat, which I do not want in a text editor.)
Re: Sublime Text 4 (Build 4126)
#28Re: Sublime Text 4 (Build 4126)
#29Earlier quoted context omitted.
Daily driving to do what type of work exactly? I've been using VS Code for years now, and while it is measurably slower (I still use sublime to handle ad-hoc grepping log files as code just won't handle that, and scrollable, highlighting and multicursor is MUCH better than smacking bash pipes together), the batteries included "It just works" approach of code means I don't really see a reason to head back. Maybe it's…
If my editor is already has batteries installed whether they were included or not, why would I need to switch to VS Code? Because it’s cool? The packages ecosystem is fine and always has been.
Re: Sublime Text 4 (Build 4126)
#30Yes it's slower and clunkier but the extensions ecosystem is worth it. And also features like intellisense, unused vars, automatic updates of imports on file renames, and a long etc of QOL features ST doesn't have interest or capacity in implementing.