Hopefully I can uninstall Notepad++ in the near future!
Visual Studio Code 1.4
101–110 of 155 posts
Re: Visual Studio Code 1.4
#102I felt bad for Sublime. It would be hard for Sublime to compete with MS's free IDE. MS finally decides to take over the open source code editor market. VSC also borrowed many features from Sublime such as its famous integrated package manager and keyboard based shortcuts.
With Visual Studio Code, I think, MS is trying to reinvent their VS family of products. Since the current Visual Studio is strongly tied to Windows and MS has accepted the multiple operating systems future (I think, in MS roadmap, revenue from Cloud Operations is one of the major factor), it's important for them to have a developer platform which works great on all the operating systems. HTML5 and JavaScript provide this opportunity to create that development tools platform for the future.
It also leaves the possibility open to port it inside browser/cloud with a lot of code reuse. If Internet Speeds improve a lot and computing in cloud becomes a lot more cheap, I think in next 10 years, for typical web projects, developers might just prefer remote development environments, which they use for coding from an App/Browser.
It's good to see that MS didn't wait to first port .Net on major Operating Systems as part of their .Net Core initiative and then write their cross platform development environment on top of that. Instead they have taken the bet on HTML5/Electron.
Re: Visual Studio Code 1.4
#103Earlier quoted context omitted.
Me too. I was a bit skeptic at first. Been a long time vim user but wanted to try something new. I now use it to code Python (I write a lot of it). It works very nicely. So much that I'm in the process of making it the official company -wide text editor for python at work.
I'm curious, what's the thought behind having an official company-wide text editor? The companies I've worked for usually take the route of "leave their choice in tools up to them", which I appreciate.
Re: Visual Studio Code 1.4
#104I've been using VSC as my daily driver for a few months now and it's great -- even on nightly builds. The most powerful features is the tasks.json. Once I learned to use it (the docs aren't good on it), I was able to utilize it to bring a more cohesive experience across many code bases. I enjoy the fact that it gives an integrated experience and allows community extensions. This is a big change from atom where everyt…
Me too. I was a bit skeptic at first. Been a long time vim user but wanted to try something new. I now use it to code Python (I write a lot of it). It works very nicely. So much that I'm in the process of making it the official company -wide text editor for python at work.
Re: Visual Studio Code 1.4
#105Whenever I try a new text editor, I run into a problem: I absolutely love the feature where it auto-completes based on other words in open windows (or other files in the open project). But there's no official term for this so I can never tell if a text editor has it. Years ago this used to be called "hippie expand", but I can't figure out a more modern name that is used. Does anyone know what Visual Studio Code calls…
Unfortunately there isn't a clear name for it. There's a bunch of sibling comments that, I think, don't quite get it right. Autocomplete is a feature. For any given autocomplete implementation, there can be a number of different sources to actually populate the AC UI. Company mode in Emacs (COMPlete ANYthing) works this way - it's a general AC framework, and different modes can provide different AC sources to it. Hip…
Re: Visual Studio Code 1.4
#106Re: Visual Studio Code 1.4
#107I've been using VSC as my daily driver for a few months now and it's great -- even on nightly builds. The most powerful features is the tasks.json. Once I learned to use it (the docs aren't good on it), I was able to utilize it to bring a more cohesive experience across many code bases. I enjoy the fact that it gives an integrated experience and allows community extensions. This is a big change from atom where everyt…
Me too. I was a bit skeptic at first. Been a long time vim user but wanted to try something new. I now use it to code Python (I write a lot of it). It works very nicely. So much that I'm in the process of making it the official company -wide text editor for python at work.
Last time I checked, there's no official Python support. There are some unofficial plugins, but none of them have true Intellisense support for Python. (e.g. a la Pycharm, or even Visual Studio Tools for Python).
I know they mentioned they were working in it a few months ago on a HN thread, but I haven't heard anything about it since.
Re: Visual Studio Code 1.4
#108Earlier quoted context omitted.
Me too. I was a bit skeptic at first. Been a long time vim user but wanted to try something new. I now use it to code Python (I write a lot of it). It works very nicely. So much that I'm in the process of making it the official company -wide text editor for python at work.
I tried it for python but the pip panel almost immediately soured me on it. Whenever I tried typing something in it, it would lock up the whole program for minutes at a time - absolutely atrocious.
Re: Visual Studio Code 1.4
#109Re: Visual Studio Code 1.4
#110Earlier quoted context omitted.
I wanted to use VSCode when I started writing TypeScript three months ago, but I found the Vim plugins super lacking, so I used Atom instead, which has a much more robust Vim plugin. However, I tried VSCode again last week after being disappointed by continued bugs in atom-typescript, and was happy to discover the Vim plugin ( https://github.com/VSCodeVim/Vim ) had made a ton of progress since I'd last given it a sho…
I don't know what turned at MS exactly but something did, at least in the department where VS and VSC are developped. I've had major bad experiences with reporting bugs to MS in the past (almost as if they had a standard 'by design' or 'wontfix' message generator). The last couple of years however, not so much. Submit a report, get a reply like 'thanks for the detailed report, we're on it' and then the bug is fixed i…