JavaScript Intellisense in HTML
Visual Studio Code 1.8
81–90 of 197 posts
Re: Visual Studio Code 1.8
#82Earlier quoted context omitted.
I love VSCode and Flow but to be honest, the Flow integration could be better (and I'm sure it will be, it's just a matter of time). There is a bunch of annoying bugs waiting to be fixed, e.g. the one about the imported types [1]. In the other hand, I don't blame the maintainers. The Flow team is a really small team and the VSCode extension is obviously not the priority. :) If you guys see this message, thanks for th…
I tried Flow but ended up using Typescript for my current project. If I were to go hard on Flow I'd probably be using Atom with Nuclide instead of VSCode. I actually like Flow slightly better but the community created type libs for TypeScript convinced me to go that direction.
I gave another try to Atom recently because of Flow and Nuclide, but I definitely prefer VSCode.
By the way, the Flow extension for VSCode is a port of Nuclide, so it's almost the same end result I guess.
Re: Visual Studio Code 1.8
#83Earlier quoted context omitted.
The debugger changed how I code. So much better than any other node debug solutions.
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.
Re: Visual Studio Code 1.8
#84Earlier quoted context omitted.
The debugger changed how I code. So much better than any other node debug solutions.
How is it better than the chrome one?
I wasn't aware it was possible to debug a running node server in the chrome browser until the addition of the 'inspect' flag in node 6. Maybe it was possible, I'm not superleet or anything.
Re: Visual Studio Code 1.8
#85Earlier quoted context omitted.
Downvotes? Would be interested to know which points were inaccurate.
I would personally never use an IDE for any of my (non-mobile) development. No way no how. That makes things like WebStorm or whatever DOA for me personally. My best guess for your downvotes is that your comment isn't only nonsense and inaccurate, but also pretty churlish.
Nonsense and churlish?
How is it mean spirited to post observations about something people were asking about?
And if something is incorrect why not just say what it is?
Re: Visual Studio Code 1.8
#86Earlier quoted context omitted.
The debugger changed how I code. So much better than any other node debug solutions.
I'm confused. Did javascript people not use a debugger before VS Code?
For client code I'd use the chrome debugger constantly. I mean for debugging a node server.
Maybe there was some way I didn't know about. There's the 'inspect' flag in node 6 now that prints out a link you can copy into your chrome browser to debug server node code.
Re: Visual Studio Code 1.8
#87Why 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…
Go away Jetbrains.
Cut it out with the "shill" accusations. Unless you have proof that somebody is astroturfing, it's a lazy accusation that is quickly becoming meaningless.
Re: Visual Studio Code 1.8
#88Why 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…
Downvotes? Would be interested to know which points were inaccurate.
Downvotes are not limited to inaccuracy; a post can fail to add value to a conversation without being inaccurate.
Re: Visual Studio Code 1.8
#89Why 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…
I only code in Go these days and it has become my default editor.
Re: Visual Studio Code 1.8
#90Being able to hide the activity bar puts VSCode into a class of editors I could imagine myself using. I tried it a couple of times in the past, and that damned big ass bar of useless icons bugged me too much (I work on a laptop screen 95% of the time, so giving up that much real estate for something I'd rather do with hotkeys is just painful). It sounds silly to dismiss it over such a small UI thing, but well...my screen is small, my eyes are getting older (so even though I have a 4k display, I can't shrink everything down without eye strain), and vim and Atom don't eat up the screen in the same way. So, I use vim and Atom (mostly vim, as old habits die hard). But, will give VSCode another try.