I didn't realize code completion / autocompletion / IntelliSense for JavaScript NPM modules required TSD. I followed the steps in this guide[0] and it seems to work fine.
Visual Studio Code is now open source
391–400 of 403 posts
Re: Visual Studio Code is now open source
#392Earlier quoted context omitted.
I love Jetbrains products, but under Linux they are nowhere near as stable as VS is on Windows, or even Jetbrains apps on Windows. They're slower, and some features don't quite work right all the time.
What? Stop lying and spreading false rumors. IntelliJ Idea and PyCharm are rock stable on Linux, they are not slower and if something isn't working then please let Jetbrains know.
It's just my experience, and I've had the same experience through multiple machines.
Re: Visual Studio Code is now open source
#393Earlier quoted context omitted.
> If they keep it up with actions such as these, there's a good chance they'll stand to be rewarded for it. And -quickly enough- they'll go back to being the old MSFT we all knew and loathed from top to bottom, and these olive branches will vanish quicker than a pile of shaved ice on a summer day. For many of us, this isn't our first rodeo. :)
It's interesting that you don't make assumptions about future "evil" behaviour of their competition.
Why is it interesting? The topic is Microsoft and Microsoft's past and present behavior.
While it is next to impossible to truly consider a topic in a vacuum, it is very common practice to focus on a particular single topic or set of topics when engaging in discussion. This practice tends to promote productive discussion by allowing the conversants to momentarily disregard issues that are largely or completely unrelated to the topic at hand.
Re: Visual Studio Code is now open source
#394Visual Studio Code does not yet support JSX, nor properly supports ES6, so it's currently unusable to modern Javascript devs. Which is a shame, because it has a lot of potential! I'll be watching this closely to see when it becomes usable in my workflow.
Dev on the Code team here. Not true. Both JSX ( http://i.imgur.com/01pAAsl.png & http://i.imgur.com/mRhOx8M.png ) and ES6 ( http://i.imgur.com/UOurihn.png ) are supported in all their glory. Note that if you are editing an ES6 project, you need to create a jsconfig.json file with at least these contents, in order to let the language services know you are doing ES6: { "compilerOptions": { "target": "ES6" } }
Do you just come out of the woodwork to blame users and then ignore their requests for help?
Re: Visual Studio Code is now open source
#395Earlier quoted context omitted.
By going to VS Code they're jettisoning themselves from the .sln (solution file), .csproj (C# project file), MS Build world. Project management and build files are being pushed into external utilities. This is kind of the way a lot of the rest the world (ruby/node/python) is going. IDEs are fine, but when you remove the need for an integrated debugger in favor of TDD the need for an IDE diminishes.
I would hardly say that TDD removes the need for an integrated debugger. Being able to inspect the state of a system the instant a test fails sounds mighty useful to me. Also, software builds being driven by an external tool has been common since at least make(1), so it's hardly a ruby/node/python thing.
I've been the new guy on teams that did not use the ide for debugging (insanity in the Java world, right?) and was perceived to be a super star because of my ability to trouble shoot and drill straight down to root causes. Learn and use your tools people!
Re: Visual Studio Code is now open source
#396Has anyone spent a lot of time with VS Code? I tried it a while back when it was first announced and have not found a reason to re-visit it yet. At the time it felt like a sublime-text alternative instead of an IDE (was it always positioned to be just an editor?) Always great to see more options though.
I never thought I'd ditch Sublime Text after using it almost exclusively since TextMate (so for the past few years). I especially never thought I'd ditch it for a Microsoft product. And perhaps most importantly, I never thought I'd use an editor that didn't have Vim keybindings (yet! it's at the top of their list, apparently).
But after using VS Code for a while now I'm pretty sure I'll keep using it, at least for Node.js development. The IntelliSense support through TypeScript definitions, the out-of-the-box support for what I consider essentials (linting, task running, emmett, etc.), and perhaps most importantly the built-in debugger make my life significantly easier.
I enjoyed working with node-inspector, but the debugging in VS Code is a lot more convenient (mostly).
To be fair, for non-node development I'd say VS Code is not yet good enough to replace Sublime Text, but that might change when enough plugins and features have been added.
What it boils down to for me is that VS Code somehow seems to be optimized exactly for my workflow. It doesn't have tons of buttons and interface elements that I don't need (as many IDE's do), and it isn't slow. But on the other hand it offers very sensible defaults that other editors such as Atom and Sublime don't have. On both those editors I've had some issues with setting up linting, debugging, IntelliSense, and a few misc. other things. The main reason for that, I suppose, is that they're all plugins developed by different people. I like how these just come with VS Code and work right away.
I'm rather baffled that I'm saying all this, considering my general aversion of using Microsoft products (even if this is based on the past). But it is what it is. VS Code is a huge timesaver for me, and (mostly) hits the sweet spot between plain, fast editor and IDE.
But please give me Vim support ASAP :).
Re: Visual Studio Code is now open source
#397Earlier quoted context omitted.
Dev on the Code team here. Not true. Both JSX ( http://i.imgur.com/01pAAsl.png & http://i.imgur.com/mRhOx8M.png ) and ES6 ( http://i.imgur.com/UOurihn.png ) are supported in all their glory. Note that if you are editing an ES6 project, you need to create a jsconfig.json file with at least these contents, in order to let the language services know you are doing ES6: { "compilerOptions": { "target": "ES6" } }
Do you just come out of the woodwork to blame users and then ignore their requests for help?
I think it was terseness rather than rudeness. But of course I can't be 100% sure.
Re: Visual Studio Code is now open source
#398Earlier quoted context omitted.
Jetbrains IDEs are highly regarded and run very well under Linux.
I'm giving my opinion and I think the experience is crap. * Jank occurs frequently * hidpi support until theoretically recently was only on the Mac * it's too often indexing * vim support is mediocre * themes are terrible and require difficult ways of installing instead of centralizing and hosting * too many tiny icons of poor design with no text unless you hover * overall UX is terrible (why can't it be like someone…
It's all subjective. Objectively, they have a huge following with many enthusiastic users. Clearly it's not the disaster that you are making it out to be.
I love some PyCharm. It's a wonderful piece of software. It is a little slow to start, and it is indeed heavy on memory, but RAM is cheap and I don't reboot hardly ever. It is 100% a first-class citizen on Linux.
Re: Visual Studio Code is now open source
#399We've been asked this by a few people, so I figured this is a good place to respond: Will PTVS (Python Tools for Visual Studio) come to VSCode? The answer is YES! This will be a major focus next year. Expect full intellisense, debugging, profiling, pkg mgmt, unit test, virtual env, multiple interpreter, Jupyter, etc. support. Disc: Python/R/Jupyter team lead https://www.visualstudio.com/features/python-vs
As a Python-lover: this is awesome. There is a need for something with good Python support in-between a full blown PyCharm and plain VIM
Curious why PyCharm isn't an option. There is really no reason to not use it. The type completion / introspection is amazing, saving at least an _hour_ per day.
Re: Visual Studio Code is now open source
#400Earlier quoted context omitted.
I'm giving my opinion and I think the experience is crap. * Jank occurs frequently * hidpi support until theoretically recently was only on the Mac * it's too often indexing * vim support is mediocre * themes are terrible and require difficult ways of installing instead of centralizing and hosting * too many tiny icons of poor design with no text unless you hover * overall UX is terrible (why can't it be like someone…
It's all subjective. Objectively, they have a huge following with many enthusiastic users. Clearly it's not the disaster that you are making it out to be. I love some PyCharm. It's a wonderful piece of software. It is a little slow to start, and it is indeed heavy on memory, but RAM is cheap and I don't reboot hardly ever. It is 100% a first-class citizen on Linux.
Having a huge number of users doesn't mean the product is what it could be. Windows 3.1 had a lot of numbers -- does that mean it was "good?"
I don't know why programmers have to deal with such shit tools. Everything is more/less the same since the 80s, with the exception of github, git, and lib centers like maven or pip. Otherwise the fundamental experience of text editors is the same, and even IDEs are more/less the same.
Meanwhile our interfaces have vastly improved otherwise. That's what I'm talking about. The bar should be higher than VS. The bar should be as high or higher than the iPhone itself.