131–140 of 312 posts
It's nicer than Atom and almost feels as snappy as Sublime. But Vim still is miles better when you have put in the work to become proficient. MacVim works great for retina screens and high color support.
I keep trying VSCode, but the main thing that keeps me going back to Atom is the fact that I have to do everything at the command line or by editing an enormous json file. Maybe I'm spoiled, but I'd much rather have a nice UI to deal with settings than have to figure out that, say, in order to show line numbers I have to modify "editor.lineNumbers" and set it to "on" (or is it "true"? or 1? I can't remember... let me…
well, it's an editor for programming. those tools are usually all about typing text, automatically completing text, and validating text. appling those idea to a json config file shouldn't be allien to a programmer.
So yeah, json or (preferably) any other markup for settings is fine so long as it hints me with possible values as I type, tooltips each variable with its meaning and so on.
Earlier quoted context omitted.
The Tasks system in VSCode is quite powerful: https://code.visualstudio.com/Docs/editor/tasks Also, the integrated Terminal (Ctrl+`) is more useful with each version.
How do you (personally) use tasks? Do you bind a key to the "Run Task" command and then type the task name in? Doesn't that feel inefficient? I'm just trying to get the edit/build/run cycle down. So far the "run" part is missing for me.
The F5 debug support is great in Node and .NET Core and there are extensions to support other language debugging. (I've heard the Go and Rust ones in particular are great, though I don't work in either language myself.)
I am surprised at the amount of semi-negative comments here. Yes, some features are yet to be implemented, (it's still a fairly young project and you can always follow GitHub issues on progress), but for an Electron app, it's surprisingly fast and capable. The Microsoft-developed Go plugin makes it the best Go IDE out there, the devs, (Ramya Rao etc.) are super responsive and really trying to resolve issues quickly.…
How does it compare to LiteIDE?
I am really loving VS Code. However, there are 2 big things I really need to give up Brackets/WebStorm entirely. 1) Jump to definition for plain JS. Both Brackets and WebStorm can find method definitions for any JS project. 2) Multiline searches. I use this quite a lot to find files that contain 2 terms on different lines.
I use vs code for Go development and it's pretty amazing. Slowly starting to use it in other languages as well, but the Go support is really 5*.
How do you like working with Go? I've been meaning to start trying it out here soon, but haven't looked very far. I'm coming from a C# background.
Earlier quoted context omitted.
VS Code is a web dev IDE. Microsoft has lost the mobile platform wars and pushing the web is a way of countering that. Plus, web and azure do go hand-in-hand, as you point out.
They lost the mobile phone, but I bet they will win the hybrid tablet/netbooks one, given how Android tablets disappeared from many consumer shops here in Germany, only to be replaced by Windows 10 ones. Samsung and Asus ones seem to have been the surviving brands and even they have Win10 devices on their brand sections.
That could just be a regional anomaly.
Earlier quoted context omitted.
VSCode vs Atom (in my opinion) isn't even a contest. Maybe Atom is super nice for some web dev stuff, but as a full flown IDE I just don't see the features.
Are you confusing VSCode with Visual Studio? VSCode is not an IDE, it's an editor, much like Atom.
It's nicer than Atom and almost feels as snappy as Sublime. But Vim still is miles better when you have put in the work to become proficient. MacVim works great for retina screens and high color support.
The VIM emulation plugin actually works reasonably well.
And just small stuff that is not working or works another way quickly gets very annoying.
I use more than basic editing.
This is an off topic, but I just learned from the article that PowerShell will soon be the default in place of cmd.exe in Windows 10. I welcome this change as I found the experience of using PS was superior to that of bash/zsh in general cases. But I hope they figured out the performance problem. As of writing, in the stable version of Windows 10, PS is perceptually slower than cmd, so I was forced to use PS only whe…
> the experience of using PS was superior to that of bash As a Linux dweller, I'm genuinely curious about this one. I've found PS inferior in just about any use case.