It's interesting they base this on NodeJS instead of Chakra.
Visual Studio Code 1.7
101–110 of 180 posts
Re: Visual Studio Code 1.7
#102Re: Visual Studio Code 1.7
#103I'm going to have to rate this as "probably never going to work". I really wanted it to succeed, because I actually like Microsoft and want a new editor, but the pure amount of ignorance this thing began with and continues to display is just too much. * Didn't launch with tabs, a plugin system, or code folding * Still no Projects or Workspace. You can open a "Folder", which behaves like a workspace, but you can only…
Re: Visual Studio Code 1.7
#104Just installed VSCode, installed a Ruby plugin (with the required ruby-debug-ide prereq), and opened a project. Debugger seems to just work. Very impressive.
Tried the vim bindings, doesn't seem to be working so well. This is something I'm used to -- vim bindings rarely work well outside of Vim. Basics like "diw" (delete inside word) don't work though.
I'll probably stick with Vim for my day-to-day editing, but you can count on me using VSCode for debugging. Not a big fan of Rubymine -- too sluggish for my tastes.
Re: Visual Studio Code 1.7
#105Re: Visual Studio Code 1.7
#106Mostly ruby developer here these days. Just installed VSCode, installed a Ruby plugin (with the required ruby-debug-ide prereq), and opened a project. Debugger seems to just work. Very impressive. Tried the vim bindings, doesn't seem to be working so well. This is something I'm used to -- vim bindings rarely work well outside of Vim. Basics like "diw" (delete inside word) don't work though. I'll probably stick with V…
Re: Visual Studio Code 1.7
#107Earlier quoted context omitted.
Since you used vim for 4 years, why didn't you add evil to emacs?
Good question. I dare to say EVIL is best Vim alternative. It's 98% percent there. But it felt wrong using Vim in Emacs. Then I wasn't using Vim nor Emacs, because I would mix commands from both (sometimes I would use C-s sometimes /?). So I told myself, if I felt comfortable using Vim, then why don't I try and learn Emacs so I can be comfortable in it too? And now after 6 months in Emacs I got to that standard produ…
Re: Visual Studio Code 1.7
#108Mostly ruby developer here these days. Just installed VSCode, installed a Ruby plugin (with the required ruby-debug-ide prereq), and opened a project. Debugger seems to just work. Very impressive. Tried the vim bindings, doesn't seem to be working so well. This is something I'm used to -- vim bindings rarely work well outside of Vim. Basics like "diw" (delete inside word) don't work though. I'll probably stick with V…
Re: Visual Studio Code 1.7
#109Microsoft and TypeScript team are doing amazing work with this editor! There are so many interesting features in it, gave it a shot few weeks ago and was really satisfied. And it is probably the first electron app that didn't feel like rest of the bunch, that are pretty much hogs and not very responsive (especially when we talk about editors and IDEs). But you know, I can't hang Emacs and Vim on the wall and leave th…
I've been using the Vim extension for quite a while and it's become fairly robust. I think it bests jVi in Netbeans.
Re: Visual Studio Code 1.7
#110Ah haha this is too funny, I just this morning caved from trying to have a functioning version of Ubuntu on the macbook work gave me, booted back into OSX, and spent a good 30 minutes scrolling through the VSCode keyboard shortcuts JSON, writing down the ones I was interested in relearning on post-its and lining them around my monitor. And not four hours later they release a pretty little printable PDF. Not very on t…