Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Visual Studio Code 1.0

code.visualstudio.com

Post reply on HN
Print view View original

331–340 of 487 posts

Re: Visual Studio Code 1.0

#331

Post by wluu »

zokier wrote: post #58

Interesting that they decided to release 1.0 before sorting out the coreclr/dotnet story. My understanding is that Mono is still the best way to write C# with VSCode, even on Windows.

If you're working on something that needs to target the full framework, then yes, Mono is the way to go. Otherwise if you're targeting the new .NET Core, then you can do without Mono with the latest pre-release versions of the VS Code C# extension (which includes debugging support).

Here's a blog post with bit more info on setting up VS Code with the pre-release version of the C# extension (and debugging support): http://www.tattoocoder.com/setting-up-asp-net-core-debugging...

Re: Visual Studio Code 1.0

#332

Post by ramchip »

jasonjei wrote: post #267
neves wrote: post #130

VSCode knockouts Atom in a dispute for becoming a developer editor in a corporate computer. Sure, you all have root password in your computer. Unfortunately, I belong to a lower race: the corporate developer. I work in a Windows 7 machine, don't have root password and there's a big wall called proxy around me. I didn't know about VSCode before this HN post, but I was trying to use a new editor instead of Notepad++. I…

How do corporate developers test and debug things without the root password? In some cases, you need to be able to start Visual Studio in UAC mode, and debug an already running process...

I worked in a bank previously. We did not have root, but we had a utility to run certain commands "as administrator". It popped up a dialog where you had to input a justification for auditing purposes.

I don't recall needing it for debugging though, even when attaching to a running process (was your process started as a different user?)

Re: Visual Studio Code 1.0

#333

Post by GFK_of_xmaspast »

Mikeb85 wrote: post #50
thewhitetulip wrote: post #24

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,…

I used emacs as my primary editor for 22 years but switched to clion last year for c/c++ development and am thinking of switching to pycharm for python stuff.

I still use emacs for quick editing, moderately complex search-and-replace in limited numbers of files (for when I don't want to bother with perl), and a handy scratchpad for throwaway things, but I don't intend to do a lot more software development in it anymore.

Re: Visual Studio Code 1.0

#334

Post by bsharitt »

ngrilly wrote: post #213
bsharitt wrote: post #126

I'm a long time vim user who's switched mostly to Atom(at least for bigger projects, vim is still my "quick fix" editor). Last time I tried VS Code(6ish months ago?), I liked it all right, but stuck with Atom because at the time the availability of vim like bindings was weak and ruby support was lacking.

What made you switch from vim to Atom?

Mostly tried it and got used to it. I liked the defaults a lot more than I do vim(nothing some plugins, a good .vimrc, etc can't fix), and I found it much more natural to use extensions that I ever did vim, so once I got Atom matching my usual vim setup I found myself extending beyond that. Most of it's probably stuff I could do in vim too, but adding extensions on whim feels a bit more natural in Atom.

I still spend a lot of time on remote systems, so vim is a big part of my tool box. There's also the weight of Atom. If I'm working on big project, I get it all loaded up and work in Atom, but if I just need to tweak a thing or two in a file, vim is still my go to.

Re: Visual Studio Code 1.0

#335

Post by beefsack »

neves wrote: post #130

VSCode knockouts Atom in a dispute for becoming a developer editor in a corporate computer. Sure, you all have root password in your computer. Unfortunately, I belong to a lower race: the corporate developer. I work in a Windows 7 machine, don't have root password and there's a big wall called proxy around me. I didn't know about VSCode before this HN post, but I was trying to use a new editor instead of Notepad++. I…

A lot of people don't want a bloated editor with too much bundled in by default. I'd be incredibly frustrated if there was some vertical selection functionality built in if it caused issues with a Vim mode extension.

Re: Visual Studio Code 1.0

#336

Post by beefsack »

I'm a long time Linux guy and absolutely hate Visual Studio, it's just clunky and unusable as Eclipse.

This post prompted me to try VS Code and I must say, I'm really impressed. There are still a few rough edges but I do understand it's still young.

As soon as the Vim extension becomes usable I'll be on board I think; things like visual selection don't appear to work correctly at the moment.

Re: Visual Studio Code 1.0

#337

Post by pbreit »

neves wrote: post #130

VSCode knockouts Atom in a dispute for becoming a developer editor in a corporate computer. Sure, you all have root password in your computer. Unfortunately, I belong to a lower race: the corporate developer. I work in a Windows 7 machine, don't have root password and there's a big wall called proxy around me. I didn't know about VSCode before this HN post, but I was trying to use a new editor instead of Notepad++. I…

Agreed that Microsoft has developed a very fine code editor and a worthy competitor to Atom & Sublime.

And if you can believe it, Adobe actually produces a decent code editor: Brackets.

Re: Visual Studio Code 1.0

#338

Post by jlubawy »

faitswulff wrote: post #292
neves wrote: post #130

VSCode knockouts Atom in a dispute for becoming a developer editor in a corporate computer. Sure, you all have root password in your computer. Unfortunately, I belong to a lower race: the corporate developer. I work in a Windows 7 machine, don't have root password and there's a big wall called proxy around me. I didn't know about VSCode before this HN post, but I was trying to use a new editor instead of Notepad++. I…

Curious if you've tried Sublime Text and your thoughts about using it in a corporate environment?

I've been using Sublime Text 3 for probably 2-3 years now at work (and home) and I love it. The only downside is it costs money but you can use it for free as long as you don't mind a popup asking you to purchase it every 10-20 saves.

I used Notepad++ for a few years before Sublime, I eventually switched because of the lack of Notepad++ support on Linux. I didn't want to have to remember the commands/shortcuts for two editors (and I avoid using Vim if I can).

Re: Visual Studio Code 1.0

#339

Post by dsl »

jasonjei wrote: post #267
neves wrote: post #130

VSCode knockouts Atom in a dispute for becoming a developer editor in a corporate computer. Sure, you all have root password in your computer. Unfortunately, I belong to a lower race: the corporate developer. I work in a Windows 7 machine, don't have root password and there's a big wall called proxy around me. I didn't know about VSCode before this HN post, but I was trying to use a new editor instead of Notepad++. I…

How do corporate developers test and debug things without the root password? In some cases, you need to be able to start Visual Studio in UAC mode, and debug an already running process...

From a security perspective, we ask: why are you developing applications that can't be ran by normal users?

For the 1% of devs working on system level stuff we provide VMs or separate physical servers that aren't joined to the corporate domain and don't have sensitive information on them.

Re: Visual Studio Code 1.0

#340

Post by jhasse »

jessegreathouse wrote: post #321
jhasse wrote: post #310

Earlier quoted context omitted.

You can run commands via the task runner. If you need a real terminal - why not simply open one and split it next to Code using your window manager?

Why not simply add a terminal pane to the editor so I don't need to?

Because most people have no need for a terminal panel, so that's a feature probably better suited for an extension.
Post reply on HN