Live data from Hacker News

Visual Studio Code 1.5

code.visualstudio.com

21–30 of 270 posts

Re: Visual Studio Code 1.5

#21

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.

I don't hold allegiances to a text editor (c'mon, it just edits text!) so I switched from Atom for a while too: I was very impressed with it (it feels so snappy, and looks so cool!). It fell over on linting some of the ES7/8 things that we use in our code base - but as soon as they fix that I will give it another serious go.

I had the same complaints and just went with the excellent ESLint plugin with a ES2016/17 friendly config instead of the default vscode linting.

Re: Visual Studio Code 1.5

#22
"Update All Extensions" Nice! It was a huge PITA before to close and reopen the editor once for every extension that had to be updated. One of my last big gripes about VSC, gone.

Re: Visual Studio Code 1.5

#23
post #9

I find it interesting that this software isn't designed with Xamarin for all platforms, but instead uses Electron. I mean I get it, the cross platform libraries are better in Electron, but it side steps their current cross platform initiative.

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.

Re: Visual Studio Code 1.5

#24
I really liked Visual Studio Code, but I couldn't really use it without a Vim plugin. So over the last few months I've been working on this one:

https://marketplace.visualstudio.com/items?itemName=vscodevi...

I think it's gotten a lot better, and if lack of vim keybindings was something that was holding you back from trying VSC, I highly encourage you to try it again!

Re: Visual Studio Code 1.5

#26

I love how VS Code has no problem working with large and even minified files (unlike some other “modern” editors). Every update is just icing on the cake. Keep up the good work!

> minified files

Did not know this. Are you telling me it un-minifies it to make it a bit more readable?

Re: Visual Studio Code 1.5

#27

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.

I liked them about equally, but Atom is really slow on my work computer and crashes on my laptop. VSC is much more stable.

Re: Visual Studio Code 1.5

#28
post #20

I find it interesting that this software isn't designed with Xamarin for all platforms, but instead uses Electron. I mean I get it, the cross platform libraries are better in Electron, but it side steps their current cross platform initiative.

Xamarin doesn't support the platform the editor was originally written for: the web.

Not super relevant to the topic, but what's with Xamarin not supporting what is arguably the most important platform? This seems like a huge weakness, especially when you can now build a React app that renders natively on web and mobile thanks to React Native.

Re: Visual Studio Code 1.5

#29

I'm still holding out for Visual Studio for Mac.APP, not crummy Xamarin or a glorified text editor.

What would full Visual Studio get you that VSC does not? IMO, the main awesomesauce of VS, and its advantages over other IDEs and editors, are

1. The first-in-class debugger

2. Intellisense

3. Really good support for Windows-specific technologies like Win32 and COM

VSC has 1 and 2 either now, or on its roadmap. As for 3, why do you want to develop for Windows on a Mac? I guess I don't understand what you need that VSC isn't already giving you, or planning to.

Re: Visual Studio Code 1.5

#30
It's unfortunate to see that the group who named their extension "Vim" is being recognized as more or less the official recommendation for Vim emulation, despite being not so good. The last time that I did a survey of feature completeness, performance, and code quality, the author of the amVim extension had a much better showing across the board--and more active involvement in VSCode extension APIs themselves. Perception and naming do matter.
Post reply on HN