Live data from Hacker News

Visual Studio Code 1.5

code.visualstudio.com

181–190 of 270 posts

Re: Visual Studio Code 1.5

#181

I switched from Atom recently and have very few complaints. One of them was the (lack of) icons in the sidebar.. the new Seti icon theme is a great addition. Ooh and they supposedly made Cmd-P searching ('Quick Open') faster. My other main complaint! Edit: Yep it's faster. I used to wait a second or two for the desired results to pop up, now they're close to instant.

Agreed! That Cmd-P slow down was just a bit too laggy. Happy to see that resolved. Fuzziness seems improved too, but I didn't do a lot of thorough testing there.

Re: Visual Studio Code 1.5

#182
post #162

Earlier quoted context omitted.

The standard recommendation seems to be to use PropTypes. And also in general, to use Babel with React programs. Would be interested to hear experiences of using Typescript with React.

In my opinion React support is progressing quickly but is not fully there yet (definitely more documentation is needed), so for the JSX part the pain is greater than the gain (especially given PropType checking already in React). As an example, to see what I mean, try to figure out how to write a properly typed Higher Order Component function. Last time I looked at it, this had no direct mention in documentation and…

It seems a little strange but you can import the propTypes of the wrapped component (argument to the HOC) into the wrapper and incorporate them into your type checking there.

Re: Visual Studio Code 1.5

#183
post #152

Earlier quoted context omitted.

Are you the author of the amVim project as its GitHub handle implies? If so, isn't a "full disclosure" needed when speaking of a "competitive" project?

How do you connect "carussell" to https://github.com/aioutecism/amVim-for-VSCode ?

I connected carussell to the crussell maintaining some fork here: https://gitlab.com/crussell/amVim as pointed elsewhere.

It would certainly be possible that he contributed code to the project given that.

Re: Visual Studio Code 1.5

#184
post #98

Earlier quoted context omitted.

Why would you use VS Code (even with vim keybindings) over vim? Is there something you can't do in vim but can in VS Code?

I have as yet been unable to get the code completion working. Were you able to?

If you mean IntelliSense in VS Code, I just got this figured out today! The official docs will walk you through it[1]. Be careful about reading blogs about how to do it, the process has changed from when you used to use "tsd". You need to click the little green light bulb at the bottom right of the editor to create a jsconfig.json file. Then install the typings module with: npm install -g typings

then install the language files you want. This will install node completion: typings install dt~node --global

Much easier than before!

[1] https://code.visualstudio.com/docs/runtimes/nodejs#_great-co...

Re: Visual Studio Code 1.5

#185

Earlier quoted context omitted.

> On this day and age many don't want to pay for tools. Strange logic: if everyone followed that train of thought, we'd all settle for whatever quality tools are available so long as the price is $0. I'd much rather pay for a valuable tool than use a subpar free tool.

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.

Eh but it existed for long before Atom and VS code. (disclaimer I paid the $70 and felt it was well worth the money at the time, these days yeah maybe I wouldn't but I still do find myself using it a lot)

Edit: To expand, sublime is still by far my favorite TEXT editor. I just don't find doing everyday text editing tasks in VSCode to be pleasant at all, its an amazing IDE though!. Atom is much better for the task but the responsiveness and large file handling capabilities of sublime makes it the clear winner. If you already paid the $70 for a licence back when atom didn't exist anyways...

Re: Visual Studio Code 1.5

#186

Anybody know how well VS Code works for C++? I really don't like how limited Sublime's linting/static analysis options are.

I tried to get C++ working in vscode but ran into trouble getting it to debug with gdb. I was looking for a smooth "hit f5 to compile and run (with breakpoints)" experience like I am used to with VS, but unfortunately there are no tutorials I could find on making that happen. The C++ extension is available, but I can't figure out what exactly it does or how to use it. It suffers from that common problem where they give you a config file, but don't tell you the possible options. There is an opportunity for a good blog post here if someone out there knows how to do this!

Re: Visual Studio Code 1.5

#187
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!)

Surprised??

With $120+ per year subscription I am surprised people use it.

Re: Visual Studio Code 1.5

#188
post #164

Earlier quoted context omitted.

I was about to try one of these fancy new browser based editors again, but now I'm confused. Shouldn't opening a directory be O(1)? I just opened the chromium trunk in sublime and it took 0.2 seconds, regardless of whether it was currently running or not. Why would one ever use a text editor that has perceptible latency when doing everyday tasks? 3 seconds isn't even latency, it's a freeze tbh.

I feel we are comparing apple to oranges here: sublime (a text editor) will simply list files & directories in the top level folder when you add a folder to the projects while an IDE (thinking mostly of Eclipse here, but I assume other IDEs aren't that different) will parse every single file to build ASTs, symbol lookup tables and all these things that you either love or cannot stand.

With ST3 we scan and index symbols in each file contained in folders that have been opened. This powers our project-wide Goto Symbol functionality and the Symbol Definition popup.

Re: Visual Studio Code 1.5

#189
When VS Code was first released, I was ecstatic at the idea of a cross-platform lightweight code editor backed by the weight of the Visual Studio brand. I wanted to move into the vim/sublime style of coding, but just couldn't get used to them despite my efforts. I was also a bit anxious that VSCode might be a bit of a publicity stunt; a way to say "See, microsoft can do cross-platform" but poorly maintained and poorly funded.

I'm happy to see it is plowing ahead steadily to a best-in-class IDE! Every time I open it, there is a new point update[1]. The documentation and tutorials are thankfully kept up to date. Out of the box it is an amazing Node.js editor and debugger. It has greatly helped me develop my Javascript skills and eased a lot of the pain I had with the lack of intellisense in that language (.net dev here). If the vision for the app was "lets create Visual Studio: Millennial Edition" I'd say: target destroyed. Whoever is in charge certainly has a vision, because this sort of app could easily get wrecked by going in too many directions at once. Keep up the great work and keep on that strategy of not listening to every single person's input ;)

[1] By that I mean I have it installed on mac/linux/win so when I open it on various computers, it usually has an update waiting. Not that I've ran it six times.

Re: Visual Studio Code 1.5

#190
post #143
post #122

Just beating a dead horse here, but I really wish Microsoft would add "hot exit" for unsaved files. It's been in Sublime Text since 2011. Nearly all my Mac apps support this feature natively. Why, in 2016, if VS Code crashes, do I lose all my unsaved files. Especially when I want to treat an instance as merely a scratch pad for ideas. Supposedly it's Under Review . Hopefully, the next release has it. https://visualst…

Several people on the vscode team (including myself) miss this feature so I'm sure it will come eventually. Also we deprecated user voice recently, the issue is now tracked in https://github.com/Microsoft/vscode/issues/101

Oh man, reading your comment made me super excited. Hopefully "eventually" will be of the sooner variety ;) Joking aside, thank you for this comment, and also your contributions to a great piece of software!
Post reply on HN