Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Visual Studio Code 1.8

code.visualstudio.com

Post reply on HN
Print view View original

181–190 of 197 posts

Re: Visual Studio Code 1.8

#181

Post by eyko »

WhitneyLand wrote: post #57

Why are people using this instead of WebStorm? It seems like: - It a little faster for Typescript (but no better TS features from what I can see). - A lot of people are trying it because it's new, or because they like MS tools. - It's free On the other hand WebStorm still has more functionality overall, a few less rough edges, and a more standard UI (some people don't like how MS Code doesn't have a tabbed doc UI). M…

Because competition is healthy and without it you'd be wishing there was an alternative to WebStorm.

Also because some of us don't like WebStorm. My experience with it has been very poor. I actually bought a license and invested time in trying to "like" it, but for my use case it was not quite there. E.g. I write a lot of Flow/TypeScript and it has always lagged behind or required me to use bleeding edge versions which were a) free anyway, so my license was unnecessary for that time span, and b) very buggy, which defeats the purpose. For vanilla JavaScript, it has the best autocompletion out there, but when you're using TypeScript or Flow there's just no advantage since practically any decent editor will give you the expected suggestions.

Boot up times are important for me because sometimes I'm in the terminal and I want to open a file, work with it, then quit (`cmd+q` or `:q`) when I'm done. WebStorm is not my friend in those cases. Vim is. Surprisingly VSCode is as well.

In WebStorm's defence, I believe the Vim plugin is one of the best out there (perhaps just second to Emacs evil mode). Other than that and its JavaScript IntelliSense... I can't really think of any other advantages. I hear some of my colleagues talk about git diffing / merge views, but to be honest I already have tools for that and I never do any git stuff in my editor unless it's Emacs + magit.

Refactoring JavaScript code might be neat with WebStorm as well but I haven't used it enough to have an opinion on it. I don't know how well it performs with TypeScript / Flow / Elm codebases but I'd be interested to see it in action, since those seem to be easier targets for refactoring than JavaScript.

Re: Visual Studio Code 1.8

#182

Post by hibbelig »

wwalser wrote: post #67

I recently moved from EMACS (after using it for ~10 years & ~6 languages) to VSCode. There are loads of things that I miss but overall it's been a fairly smooth transition. I'm moving because I spend most of my time writing javascript and felt that no combination of emacs modes allowed me to keep up with a proper IDE. Emacs is a tool to learn once and use for a lifetime (and I will continue to use it for other editin…

For the IDO part: If you open a folder in VS Code, then you can use Ctrl+P or Ctrl+T (I keep forgetting which), and that allows you to type part of the file name, and then it will find it. The best is, it searches the entire subtree of the folder you opened.

Re: Visual Studio Code 1.8

#184

Post by nojvek »

nkg wrote: post #177
nojvek wrote: post #150

Earlier quoted context omitted.

I don't work on vscode directly, have contributed bug fixes and features but if you'd like to be considered for a team inside visual studio working on web diagnostics, please ping me.

What is "web diagnostics" about ?

Chrome devtools equivalent of edge browser: F12 Developer tools.

Re: Visual Studio Code 1.8

#186

Post by wwalser »

suprfnk wrote: post #157
wwalser wrote: post #115

Earlier quoted context omitted.

The command palette seems like the sort of thing that'll have more power than I'm currently giving it credit for. How do you create a file outside of the directory that you're currently editing?

If you create a new file, when pressing save, you get a save dialog. In there you can navigate to the folder where you want to save the file.

I'm aware. If you follow the thread, we're talking specifically about creating a new file using the command pallet. Also, I mentioned above that, while I'm aware of the ability to create a file using finder, I'd rather not.

Re: Visual Studio Code 1.8

#187

Post by hashhar »

coldtea wrote: post #167
coldtea wrote: post #156

Earlier quoted context omitted.

> In general, ignorance is not a pejorative but if a candidate walk into an interview claiming to be an expert and I find out that you debug in anger using console log, I'm calling bullshit. Some of the best programmers advocate for printf over debuggers... And some of the crappiest programmers run around the debugger for hours with no idea what could be wrong in the program, stepping blindly here and there...

To explain this further, I think printf is more focused and direct than running around in the debugger. You need to have a clearer idea of what you're looking for in advance and know how to exclude parts of the program as possible culprits, which I think helps with debugging in general. And, come to think of it, with hot code reloading, printf can be just as immediate, but more direct and focused, than using the debu…

I agree. The best printf debugging I've seen is Mike Conley from Firefox Live Hacking. He has quite a few debugging tricks up his sleeve.

[1]: https://www.youtube.com/channel/UCTDXvmarLFnox4AO0w2NuiQ

Re: Visual Studio Code 1.8

#188

Post by komali2 »

h1d wrote: post #173
komali2 wrote: post #83

Earlier quoted context omitted.

I don't know, I don't use intelliJ and I don't want to pay for webstorm. Somebody else probably knows. Anyway I like how low-memory-on-the-disk and low RAM usage VScode is, so I probably wouldn't enjoy intelliJ and webstorm for those reasons. I felt like even sublime was too bulky for me. Maybe they're good for other people and that's fine, but vscode just ticks all the right boxes.

Out of curiosity, what is the reason, you don't want to pay? Is it your financial restriction or that there is something philosophical about sticking with free stuff whenever possible? Once you figure that if anything makes your days better by spending $10 or so a month, not choosing the best tool for the job sounds simply dumb. I have a friend who sticks with plain vim uncustomized because he doesn't want to deviate…

I'm all about paying for things that add value - I haven't been convinced webstorm will add value.

I am very fortunate in my means right now, but I come from a poor family, and spending money is emotionally trying for me. I gain pleasure from pushing my monthly expenses down as tight as I can. It seems melodramatic but paying for webstorm might just stress me out - I'd constantly feel a need to justify it, like when I tried subbing to World of Warcraft - I'd catch myself calculating fun per dollar. Euck.

Anyway I'm a simple front end dev so I don't think it's necessary for now. As I branch out into Python perhaps Webstorm's tools will add tremendous value, I have seen some cool stuff but I just don't need it for now.

Re: Visual Studio Code 1.8

#189

Post by coldtea »

maxxxxx wrote: post #174
coldtea wrote: post #167

Earlier quoted context omitted.

To explain this further, I think printf is more focused and direct than running around in the debugger. You need to have a clearer idea of what you're looking for in advance and know how to exclude parts of the program as possible culprits, which I think helps with debugging in general. And, come to think of it, with hot code reloading, printf can be just as immediate, but more direct and focused, than using the debu…

It sounds like you are trying to sell lack of a debugger as a feature that forces devs to to be more aware and more precise. Then we should maybe go back to writing code on paper first, create punch cards, submit to the mainframe and get the result next day? Then you have an even better idea of what your program does. Debuggers are a valuable tool that nowadays should be standard.

>Then we should maybe go back to writing code on paper first, create punch cards, submit to the mainframe and get the result next day?

Just because someone advocates taking a step back in some particular issue (and for specific reasons they argue about) doesn't mean it logically follows that they advocate going all the way back.

Two things: "slippery slope" fallacy and "marginal returns".

I'm pretty sure we can find some ways in which you yourself advocates NOT using some modern language feature in favor of an older practice (e.g. you might be against visual programming languages). Does that mean you are ultimately in the same "punch cars" camp as you suggest I am?

Re: Visual Studio Code 1.8

#190

Post by kabes »

komali2 wrote: post #83
kabes wrote: post #16

Earlier quoted context omitted.

How is it better than the one in IntelliJ/webstorm?

I don't know, I don't use intelliJ and I don't want to pay for webstorm. Somebody else probably knows. Anyway I like how low-memory-on-the-disk and low RAM usage VScode is, so I probably wouldn't enjoy intelliJ and webstorm for those reasons. I felt like even sublime was too bulky for me. Maybe they're good for other people and that's fine, but vscode just ticks all the right boxes.

Well, then it's kind of a far stretch to claim vscode debugging is better than ANY other solution if you haven't tried them all. Not even the most popular once like webstorm.
Post reply on HN