News for hackers. Stuff that matters.
Re:Sublime Text 3.0 by eptakilo on Wednesday September 13, 2017 @09:26AM (#15237994)
I primarily use VSCode as my editor but I used Sublime back in the days.

I haven't touched it in a while. How do these two editors compare lately?

Re:Sublime Text 3.0 by reificator on Wednesday September 13, 2017 @09:43AM (#15238125)
I'm in the same boat, though I find it unlikely that I would go back to Sublime at this point.

VSCode is free, (mostly) MIT, has a unified debugger, great git support, integrated terminal emulator, and a nice healthy extension community.

Sublime is cheap for how often you'll use it, but not free. It's proprietary. Git support even with paid plugins is lacking, especially compared to VS Code.

I'm glad I bought Sublime when I did, but I'm also glad I found VSCode when I did. If there's a choice between FOSS and proprietary, and the FOSS project already works better, the proprietary option is unlikely to make a comeback for me.

Re:Sublime Text 3.0 by yodsanklai on Wednesday September 13, 2017 @10:05AM (#15238334)
Same here. I switched from Sublime to VSCode a few weeks ago after reading some comments here on HN. I don't think I will go back to Sublime for the reasons you mentioned. I also have the feeling that thanks to a fast increasing community the extensions are more polished (in particular, I like the vim mode better).

Sublime is indeed faster and more lightweight but that's not enough for me to keep using it.

Re:Sublime Text 3.0 by bsimpson on Wednesday September 13, 2017 @11:37AM (#15239301)
Really? One of the things that has kept me on Sublime is SublimeGit. It's fantastic.
Re:Sublime Text 3.0 by dham on Wednesday September 13, 2017 @09:35AM (#15238067)
Sublime is still the fastest(opens instantly), and personally it looks better than VSCode with the new adaptive themes. Font rendering on MacOS is native in Sublime instead of the fake blurry stuff you get with Electron.
Re:Sublime Text 3.0 by gcp on Wednesday September 13, 2017 @12:53PM (#15240121)
Font rendering on MacOS is native in Sublime instead of the fake blurry stuff you get with Electron.

Wheee, I'm not the only one bothered by this! It's bad on Windows too, though Linux is fine. It affects all Electron based programs, including Chrome itself.

Re:Sublime Text 3.0 by yodsanklai on Wednesday September 13, 2017 @10:05AM (#15238340)
It is slightly faster, but I didn't notice any difference with the fonts.
Re:Sublime Text 3.0 by ionised on Wednesday September 13, 2017 @11:59AM (#15239548)
'slightly' is a serious understatement
Re:Sublime Text 3.0 by konart on Wednesday September 13, 2017 @11:07AM (#15238943)
If we are talking about opening big files - Sublime times faster than VSC and miles faster than Code, which still fails at files bigger then 10mb often.
Re:Sublime Text 3.0 by bchang55 on Wednesday September 13, 2017 @12:47PM (#15240058)
VSC recently put in a large file feature. Which disables many of the standard text editing features to open up these files faster.

I'm not sure if this addresses files bigger than 10mb though.

Re:Sublime Text 3.0 by konart on Tuesday September 26, 2017 @11:29AM (#15339507)
I'm using VCS for some time now (and was at the time of the previous comment), but it's still slow when compared. They did a great job and left Atom (I ment Atom when I said Code, lol) behind, but there is still a huge room for improvement.
Re:Sublime Text 3.0 by faaq on Wednesday September 13, 2017 @10:02PM (#15244476)
Yeah, it does and pretty well in latest releases.[0]

[0] - https://github.com/Microsoft/vscode/issues/6474#issuecomment...

Re:Sublime Text 3.0 by pkrefta on Wednesday September 13, 2017 @09:30AM (#15238024)
In terms of opening speed at least - it still crushed both VSCode & Atom.
Re:Sublime Text 3.0 by SketchySeaBeast on Wednesday September 13, 2017 @10:01AM (#15238303)
I think it really depends on what you're using them for. I know I use both every day. I find myself using VSCode for more of my coding (taking advantage of intellisense and the built in debugger for my python work), while I find that Sublime has a much better "find in files" (as we use CVS for version control), and its general better for opening one-off files or lengthy debug logs with its amazing speed, and having enough respect to not leave little .vscode folders everywhere you tinker.
Re:Sublime Text 3.0 by marsrover on Wednesday September 13, 2017 @10:30AM (#15238607)
I downloaded Sublime 3 to try it out, just now. The first thing I did was install Vintageous. I hit `{` and the cursor didn't move.

I love Sublime and used it for many years. It's fast, it looks good, and it's a great editor. It's hard to find an extension ecosystem like VSCode, though. I doubt I'll be returning to Sublime.

Re:Sublime Text 3.0 by wedowhatwedo on Wednesday September 13, 2017 @12:06PM (#15239624)
https://github.com/guillermooo/Vintageous

"Vintageous has been discontinued."

I wouldn't blame the problem you had on Sublime. I can start up Sublime with all my plugins, press '{' and it works as expected.

Re:Sublime Text 3.0 by rdavis on Wednesday September 13, 2017 @07:06PM (#15243574)
Check out NeoVintageous [0]. It's the continuation of Vintageous and adds some great features.

[0] https://github.com/NeoVintageous/NeoVintageous

Re:Sublime Text 3.0 by SippinLean on Wednesday September 13, 2017 @10:55AM (#15238854)
For front-end web development, OOTB VSCode is much better, in terms of features (though you could probably get ST to be that way with a number of plugins).

ST is still a lot faster, but now that VSCode has introduced multi-folder workspaces there aren't a lot of features I miss anymore.

Re:Sublime Text 3.0 by alexashka on Wednesday September 13, 2017 @11:09AM (#15238960)
Sublime was the text editor for web dev because there wasn't a nice, free IDE.

VSCode is that IDE - long live Sublime.

It'll take a while to switch over but the writing is on the wall as far as I'm concerned - Sublime will be fondly remembered for it's novel features.

Re:Sublime Text 3.0 by cdelsolar on Wednesday September 13, 2017 @02:10PM (#15240945)
Ok sure. I just immediately paid the (underpriced) $30 for the license upgrade.