Live data from Hacker News

Visual Studio Code 1.0

code.visualstudio.com

161–170 of 487 posts

Re: Visual Studio Code 1.0

#161

Does anybody else use several editors all the time? I use Emacs, Vim, Eclipse, Atom, and Intellij. I don't stick to one. I wish I could stick to one editor but there is always some editor that does a way better job at a particular task. Each editor has its killer feature. I have tried turning emulation of emacs/vim on many editors to provide consistency and its never been really good. Thus I have several "default" ke…

Aside from different tools having different strengths, I enjoy learning to use new software. I think if I used one tool for everything I would get bored with it. That said, learning new keyboard commands is sometimes a real PITA. When I'm tired, I sometimes find myself trying to close Visual Studio or Sublime Text with :q.

Then you have people like me that use so many different editors because I'm burned out on learning to use new software.

For a task I'll use whichever editor needs to least amount of learning, re-learning, and fiddling.

It amazes me that there was a time where I learned Emacs just for Clojure.

Re: Visual Studio Code 1.0

#162
post #4

Still no CLI mode for editing text. Vim has had this for years. How am I supposed to integrate this behemoth into my work flow if I can't even run it in a terminal? It's just too clunky for my taste. It's also hilarious that Atom gets shat on for data collection when no one cares that VS does it too. Microsoft can do no wrong, only OSS projects have standards to live up to.

> Still no CLI mode for editing text

Normally I'd be the first jumping on Microsoft products and criticize them but this is a strange statement. Most of what you can find in VSCode runs on nodejs so if you want a specific features in a CLI you don't need VSCode, just install whatever nodejs lib you need and use it from the CLI.

Re: Visual Studio Code 1.0

#163
I'm quite surprised by how much smoother VSCode is than Atom despite being built upon the same platform, I just wish it had tabs and split tab groups, then I could give it a go for a full day and decide whether I like it or not.

Re: Visual Studio Code 1.0

#164
post #152

Version 1.0 seems to no longer support syntax highlighting for C# files. Why would they do this? Or am I the only one seeing this?

They moved the C# support into an extension in the previous version, you just need to install. https://code.visualstudio.com/Docs/languages/csharp

Ah, thanks.

Re: Visual Studio Code 1.0

#165
post #88

Earlier quoted context omitted.

>Vim and Emacs are still superior if you want to put the time >in, TBH, not every developer is willing to become a power user or interested to learn an IDE instead of the language itself. Being someone who worked on VStudio alot and now on Linux/Mac based tools, I can safely say that Microsoft tools are Developers friendly most of the time. It's good they are introducing same touch for Linux/OSX community.

That is fine, I think it is great that IDEs exist for easy editing and debugging. But power users will always exist in the programming community. These people will naturally use Vim and Emacs because they support the customization levels needed for complex programming workflows.

In my experience novices have an easier time learning programming with an intuitive IDE, but experienced users use whatever makes the most sense given the task at hand, which in many cases might also be an IDE. They're just different tools with different pros and cons, and each of those pros and cons are weighted differently depending on what you're trying to accomplish.

Very few programming workflows are so complicated that it is simply not possible to do something without first creating your own highly customized environment within Emacs. However, very, very many programmers do have a lot more fun screwing around with customizing their work environment (editor, window manager, shell, etc.) than using that environment to get actual work done (myself included).

Which is not to say that Vim and Emacs aren't awesome tools, I just wouldn't generalize anything about anyone based on the tools they use.

Re: Visual Studio Code 1.0

#166
post #81

Earlier quoted context omitted.

That's what, gone are the days when we'd spend hours and hours to learn the little little ways of vi and the myriad functions in emacs. Now we need to get things done, can't afford to sit down and study the entire functions of vi and emacs. I don't mean to troll but after switching to vscode and the go plugin I learned go webdev and wrote this small intro book, http://github.com/thewhitetulip/web-dev-golang-anti-text…

What, exactly and without sweeping generalities, does it do that is a transformative step over Sublime Text or Atom? Or, hell, even Kate?

1. atom is slow and clunky it hangs when I paste a 10000 line sql insert statements 2. sublime text: sorry didn't try

vscode's benifits:

blazingly fast modern design works on linux/mac too little features like ctrl+P which lets you to jump to functions rather than play with files, I didn't know any other editor which allowed this feature to be there.

It is a great way to code if you don't want or can't use vi/emacs, I don't have the luxury to learn all the nook and corners of emacs, I started using Go plugin in vscode and today I have built go apps and written partially completed book: http://github.com/thewhitetulip/web-dev-golang-anti-textbook...

i tried giving vi a chance, but nope. couldn't bear it for more than a day, large webapps require a UI IDE, vscode > everything else I tried till now

Re: Visual Studio Code 1.0

#167
post #69

I'm your standard unix greybeard, the sort that uses org-mode to outline-structure their emacs config (that's actually what I do, not even a hypothetical), so I approached VSCode with skepticism. I have actually been really impressed. It's fast and responsive, even on Linux, and the TypeScript tooling is fantastic. I think with a bit more UI work (like vi keybindings) it could potentially become my preferred editor.

I've seen the vi keybindings complaint a few times in here, and it's my major complaint as well. There are a few plugins, but they just aren't even close to usable in my opinion.

Re: Visual Studio Code 1.0

#168
post #82

Does VSCode 1.0 still come with the tracking and analytics (phone home stuff) that cannot be turned off?

It was possible to disable that pre-1.0 by adding the following to your config file:

"telemetry.enableTelemetry": false

Re: Visual Studio Code 1.0

#169
post #50

VSCode has done the thing that nobody expected MS to do, change the way code was written on Unix/Linux. I love linux/unix, but the problem always was with the lack of an awesome text editor cum IDE, yep there is eclipse but it is too clunky, I do not like sublime as it isn't FOSS (call me crazy), gedit took way too much memory, geany is fast and mean but the UI sucks plus functionality isn't that great. Enter VSCode,…

Ummm, no. VS Code is a decent editor, nothing more. It certainly doesn't transform the way code is written on Unix/Linux. Vim and Emacs are still superior if you want to put the time in, and both have non-terminal interfaces. They can also be both customized to be whatever you want them to be, there's not really a limit to their functionality except what plugins are already written. Ditto for Atom, though of course,…

"Vim and Emacs are still superior if you want to put the time in, and both have non-terminal interfaces."

I don't need an instruction manual to figure out how to close VSCode.

Re: Visual Studio Code 1.0

#170

I've been writing OCaml for a while and seeing that VSCode has a pretty sweet integration for F# gets me quite excited. Is there anyone here who's running F# on Linux / OSX and can share their thoughts?

It's amazing, especially with the Ionide ( http://ionide.io/ ) extension. By far the most pleasent F# experience you'll find on ANY platform. I use it on both Windows and OS X and it's been very enjoyable.

The F# support is what got me to try vscode at all. Before that, I was skeptical about all js-based editors (being an emacs guy), but I was pleasantly surprised at how well this vscode+ionide setup works.

Visual Studio is still a bit nicer with regards to handling all the .fsproj stuff, and visually showing you the order of your files, but the editing itself on vscode is definitely on-par with it.

Post reply on HN