News for hackers. Stuff that matters.
Re:Disassembling Sublime Text by ino on Sunday December 04, 2016 @02:36PM (#13101368)
If I already have a Sublime license, and I'm happy and it fulfils my needs perfectly, what would I gain in spending the time to try to get my workflow working in VSCode if it still hasn't caught up, as you say?
Re:Disassembling Sublime Text by bubersson on Sunday December 04, 2016 @03:27PM (#13101621)
If it fulfills your needs perfectly then there's no need to change. It may be still worth playing with a bit and doing tooling investigation to find out if there are some super useful features for your case.

I switched to vscode from sublime recently, because it has much better autocompletion and "goto definition" especially when working with JS and TypeScript code, which is exactly what I need. Other than that I was able to replicate all features from Sublime (e.g. multipoint editing) and I'm not aware of any missing feature from what I used in Sublime. One con is that vscode is slower to start and slower to open up a file.

Re:Disassembling Sublime Text by paulddraper on Sunday December 04, 2016 @02:48PM (#13101432)
> I'm happy and it fulfils my needs perfectly

Have you not answered your own question?

Re:Disassembling Sublime Text by adamrezich on Sunday December 04, 2016 @02:41PM (#13101400)
Up-to-date plugin ecosystem, especially if you write code in trendy languages.

But if your workflow ain't broke, don't fix it, right?

Re:Disassembling Sublime Text by nathancahill on Sunday December 04, 2016 @02:53PM (#13101463)
It's closer to an actual IDE for JS than Sublime is (even once you install a bunch of ST plugins). Especially for TypeScript. That said, if Sublime is working for you, stick with it.
Re:Disassembling Sublime Text by xwvvvvwx on Sunday December 04, 2016 @06:23PM (#13102328)
having a multi language debugger integrated into my editor was a huge game changer for me.