Live data from Hacker News

Visual Studio Code 1.5

code.visualstudio.com

221–230 of 270 posts

Re: Visual Studio Code 1.5

#221
post #32

VSCode + TypeScript is an amazing experience for us poor JavaScript developers that never enjoyed proper autocomplete and refactoring in our editors. Writing JavaScript feels like writing random bash scripts with no help now. TypeScript is freaking awesome and you should start using it! :)

Try WebStorm. I'm surprised at how few people use it, given the quality of the autocomplete and code assistance (and the fact that it works just as well with ES6 as it does with TypeScript!)

I can't get over the Eclipse-ish yet unconfigurable UI.

Re: Visual Studio Code 1.5

#222
post #23
post #9

Earlier quoted context omitted.

It predates MS buying Xamarin, I think.

That's unrelated to why they chose TypeScript. They chose TypeScript because the editor was built for Visual Studio Online.

Good point. Forgot about Monaco for a moment here.

Re: Visual Studio Code 1.5

#223
post #169

Earlier quoted context omitted.

Would creating large applications in WebStorm break things if I wanted to use VSCode in the future or alongside?

That's one of my big gripes with IntelliJ - _please_ use standard compiling/building tools. At least use bash/batch files. I want to be able to build my projects if I ever decide that I don't need it anymore

I don't understand this comment. How are the build tools Jetbrain's fault? Confused...

Re: Visual Studio Code 1.5

#224

Earlier quoted context omitted.

VSCode is open source software. WebStorm isn't. I love JetBrains IDEs but I sure as hell prefer using tools that I can fix or modify myself.

Jet-brains products have a gigantic plugin ecosystem that allows you to add whatever functionality you want..

Well, not everything. Language support cannot be implemented by relying on an external service (like the typescript service), it has to be implemented in a very specific way.

They are extensible, sure, but not very flexible.

Re: Visual Studio Code 1.5

#226
post #117

Earlier quoted context omitted.

what do you mean, can you explain? isn't that correct behavior if you rename the file?

They mean the file name is the same and you end up with several files in the download folder without knowing what's the one you need.

If only we could sort files by date or something like that.

Re: Visual Studio Code 1.5

#227
post #32

VSCode + TypeScript is an amazing experience for us poor JavaScript developers that never enjoyed proper autocomplete and refactoring in our editors. Writing JavaScript feels like writing random bash scripts with no help now. TypeScript is freaking awesome and you should start using it! :)

Try WebStorm. I'm surprised at how few people use it, given the quality of the autocomplete and code assistance (and the fact that it works just as well with ES6 as it does with TypeScript!)

I use both, well not so much Webstorm, but IntelliJ for Java/GWT application stack and Visual Studio Code for almost everything else (Python, JS, etc).

Works pretty well, although I think I could increase productivity if I align the keybinding for both of them (i.e. quick open, find, etc)

Re: Visual Studio Code 1.5

#228
post #219

Earlier quoted context omitted.

It's a common fallacy to associate quality with price. Generally yes, but not always. Sublime Text certainly isn't 70 dollars better than Atom or VS Code.

I wasn't only associating quality with price, but also pointing out that many of the 2016's Emacs and vi users would not use them if they were only available as commercial software. Regardless of their quality, because the actual IT generation wants to earn money with tools they got for free (beer), while other professions people do pay for their tools.

> Regardless of their quality, because the actual IT generation wants to earn money with tools they got for free (beer), while other professions people do pay for their tools.

You seem to feel strongly enough about this to repeat it nearly word-for-word in multiple comments. Trust me, every profession wants to pay less for its tools. And no one, in IT or out, is choosing their tools "regardless of quality".

Re: Visual Studio Code 1.5

#229
post #212

Earlier quoted context omitted.

Try WebStorm. I'm surprised at how few people use it, given the quality of the autocomplete and code assistance (and the fact that it works just as well with ES6 as it does with TypeScript!)

WebStorm is very heavy, and its TypeScript support has some issues that were deal breakers for me (last time I tried).

When was the last time you tried? They are very quick at reacting to (good) bug reports. I've filed almost a hundred by now and I decided to pay them because of my experience in their reaction to bug reports. With each new EAP (early access) and release TypeScript always has a lot of fixes, so it's obvious to me TS has a high priority to them.

Also see here: https://news.ycombinator.com/item?id=12292148

Re: Visual Studio Code 1.5

#230
post #227

Earlier quoted context omitted.

Try WebStorm. I'm surprised at how few people use it, given the quality of the autocomplete and code assistance (and the fact that it works just as well with ES6 as it does with TypeScript!)

I use both, well not so much Webstorm, but IntelliJ for Java/GWT application stack and Visual Studio Code for almost everything else (Python, JS, etc). Works pretty well, although I think I could increase productivity if I align the keybinding for both of them (i.e. quick open, find, etc)

You know you can use IntelliJ with python (you get pycharm like experience)
Post reply on HN