News for hackers. Stuff that matters.
Re:Visual Studio for Mac by jpalomaki on Monday November 14, 2016 @02:48AM (#12948163)
Interesting, but I can also see some risks with their approach. Now they have three different Visual Studios with completely different technology stacks.

1) Visual Studio for Windows (C++, I assume?)

2) Visual Studio Code (Javascript, Atom)

3) Visual Studio for Mac (C#)

Re:Visual Studio for Mac by Kipters on Monday November 14, 2016 @02:54AM (#12948188)
Visual Studio for Windows is written in C# with WPF, but your point is still valid since they are two different codebases
Re:Visual Studio for Mac by ygra on Monday November 14, 2016 @03:19AM (#12948306)
Visual Studio for Windows is mostly C++, plus a lot of other things. Heck, there's JavaScript in there, too.
Re:Visual Studio for Mac by Kipters on Monday November 14, 2016 @03:21AM (#12948316)
It used to, they moved to WPF with Visual Studio 2010, now it's mostly WPF with some legacy parts that are still in C++
Re:Visual Studio for Mac by satysin on Monday November 14, 2016 @03:35AM (#12948358)
AFAIK the editor (shell) is WPF (C#?) but the internals are still mostly C++/Win32.
Re:Visual Studio for Mac by int_19h on Monday November 14, 2016 @03:49AM (#12948416)
The shell still has a lot of C++ in it, yes (but also a lot of C#).

But the shell is a relatively small part of the entire IDE - the bulk of it is the extensions that actually provide support for various languages and technologies. Those also have some C++, either as legacy code, or because the team just preferred it, but by now C# is definitely the majority of it, and it keeps trending in that direction.

A lot of it can be very non-obvious and defying common sense. For example, if you take VS 2013 (pre-Roslyn), the C++ project system was written entirely in C#, while the C# project system was written mostly in C++.

Re:Visual Studio for Mac by Kipters on Monday November 14, 2016 @02:13PM (#12952420)
Even in the .NET Core world, the managed runtime is written in C++, the native runtime (for .NET Native) is written in C#.
Re:Visual Studio for Mac by Kipters on Monday November 14, 2016 @03:41AM (#12948382)
Seems plausible, I don't know enough details to argue this.
Re:Visual Studio for Mac by thebeardedone on Monday November 14, 2016 @02:59AM (#12948212)
Hmm I have been googling for the last 15 minutes to find the difference between visual studio and visual studio code and cant seem to find a concrete answer. I thought yours was actually a hint at what it is aimed for but when you go to:

http://code.visualstudio.com/

it actually says it supports c++,c#... I still dont get what the difference is..

Having only ever developed on linux I am actually slightly excited to use an IDE like visual studio after seeing some people at work use it..

Re:Visual Studio for Mac by Kipters on Monday November 14, 2016 @03:05AM (#12948249)
Visual Studio and Visual Studio for Mac are IDEs written in C# and they support C#, C++, VB.Net and many other languages.

Visual Studio Code is a text editor built in TypeScript and based on Electron. It supports a broad range of languages, but it's an advanced text editor, not a full fledged IDE

Re:Visual Studio for Mac by madeofpalk on Monday November 14, 2016 @03:05AM (#12948244)
Visual Studio Code is more like a fancy text editor rather an a full IDE. It's more like Sublime Text or (technically) Atom, rather than an IDE like Visual Studio for Windows or XCode.
Re:Visual Studio for Mac by erikbye on Monday November 14, 2016 @03:16AM (#12948296)
You do know the difference between a text editor and an IDE? That's the difference between VS Code and VS.
Re:Visual Studio for Mac by Nilzor on Monday November 14, 2016 @03:51AM (#12948425)
Do YOU know the difference? Would it hurt to be more concrete? I'm going to venture a guess based on my assumptions, which are probably wrong, but then we can at least start a discussion:

-VS Code doesn't support solution-wide refactoring like renaming classes or moving a method from one class to another

-VS Code doesn't support runtime debugging (breakpoints)

-VS Code doesn't have a visual editor

-VS Code doesn't have memory or performance profiling tools

-VS Code doesn't have source control integration

-VS Code doesn't have an integrated build tool (MSBuild)

-VS Code doesn't have NPM or Nuget integration

Re:Visual Studio for Mac by lloeki on Monday November 14, 2016 @04:30AM (#12948578)
Disclaimer: I'm not using the C# extension

> VS Code doesn't support solution-wide refactoring like renaming classes or moving a method from one class to another

F2 "Rename Symbol" (works on Go with gorename). Can't imagine using Roslyn doesn't (or won't soon enough) allow the same. From the readme:

Great C# editing support, including Syntax Highlighting, IntelliSense, Go to Definition, Find All References, etc.

> VS Code doesn't support runtime debugging (breakpoints)

It does. CMD+Shift+D goes to the Debug sidebar. CMD+Shift+P Debug shows a bunch of commands. From the readme:

Debugging support for .NET Core (CoreCLR). NOTE: Mono and Desktop CLR debugging is not supported.

> VS Code doesn't have source control integration

CMD+Shift+P git whatevs is used daily here as well as Ctrl+Shift+G for the git sidebar that can show (editable) diffs. Both the gutter and scroll bar are annotated with git info.

> VS Code doesn't have an integrated build tool (MSBuild)

MSBuild comes with .Net Core and is (probably) invoked with the language-agnostic CMD+Shift+B (run build task). C# ext may have more.

> VS Code doesn't have NPM or Nuget integration

There are both NPM and NuGet extensions available.

Now of course if what you want is all of this nicely packaged and wrapped in a GUI, well, obviously VS Code is not an IDE (as VS is) but that's precisely its value proposition.

Re:Visual Studio for Mac by Nilzor on Monday November 14, 2016 @05:02AM (#12948689)
>Obviously VS Code is not an IDE (as VS is)

OBVIOUSLY? :D VS Code starts looking more and more like an IDE to me :-) Still looking forward to hear what people define as an IDE!

Thank you for your detailed response by the way, not picking on your post, just curious what everybody finds so "unIDEish" about VS Code.

Re:Visual Studio for Mac by ldev on Monday November 14, 2016 @05:30AM (#12948792)
I stands for "Integrated" in IDE. Project generation, code inspection, source control, database access, refactoring, debugging, test running, etc are integrated.

Visual Studio Code generates project via third party tool - dotnet new. Refactoring, code completion is done via third party tool - Roslyn (?). Etc. It's an editor with plugins. Unlike Visual Studio or Jetbrains Rider.

Re:Visual Studio for Mac by ygra on Monday November 14, 2016 @06:04AM (#12948961)
So Eclipse isn't an IDE either because all functionality is in individual plugins?
Re:Visual Studio for Mac by ldev on Monday November 14, 2016 @10:46AM (#12950482)
Eclipse always been resource hungry sublime text java clone.
Re:Visual Studio for Mac by erikbye on Monday November 14, 2016 @12:04PM (#12951255)
Are you saying Sublime Text existed prior to Eclipse?
Re:Visual Studio for Mac by erikbye on Monday November 14, 2016 @05:22AM (#12948757)
It would not hurt, but it would be an arduous and unnecessary task. Most people know the difference, and if you do not, you can read the Wikipedia article on IDE. There is no need to have a discussion on the differences, it is not remotely interesting or fruitful.
Re:Visual Studio for Mac by Nilzor on Monday November 14, 2016 @02:04PM (#12952346)
I guess what annoyed me was that after thebeardedone said he'd googled for 15 minutes trying to figure out the difference between VS Code and VS, 4 answers to his post gave absolutely no clarification as to what the differences were, including yours. If you look up the definition of an IDE on Wikipedia, VS Code falls into that category.
Re:Visual Studio for Mac by jhasse on Monday November 14, 2016 @04:00AM (#12948464)
VS Code supports runtime debugging.
Re:Visual Studio for Mac by afishisafish on Monday November 14, 2016 @04:13AM (#12948514)
VS Code supports GIT integration
Re:Visual Studio for Mac by ZenoArrow on Monday November 14, 2016 @03:07AM (#12948259)
>"it actually says it supports c++,c#... I still dont get what the difference is.."

The GP was looking at the languages the tools were written in, not the languages they support.

For what it's worth, I believe 'TypeScript + Electron' would be a closer description of what VSC was based on.

Re:Visual Studio for Mac by tracker1 on Monday November 14, 2016 @06:08AM (#12948985)
Visual Studio Code is less than a full featured IDE, and more of a very advanced code editor with told integration... The ui is much more minimalist in VS Code than full VS, Eclipse etc.

It's not that it doesn't do the job, it's just a different workflow.

As it stands, VS Code is probably the best tool for JS/Node projects or today imho. And from what I've seen, one of the better options with plugins for go and rust.

It's also available for Windows, Mac and Linux... Much faster/lighter than others, including Atim.

I'm a fan of code, but no ties to ms...

Re:Visual Studio for Mac by zgramana on Monday November 14, 2016 @11:29AM (#12950879)
Lot of overlap, but VS Code has a much bigger ecosystem/community. Xamarin/Visual Studio has advanced debugging features like thread inspection, "immediate" console for executing commands while the program execution is paused, profiler, App Store submission, and stuff like T4 templates, etc.
Re:Visual Studio for Mac by cwyers on Monday November 14, 2016 @10:51AM (#12950544)
But if you're writing C# in any of them, you're using the Roslyn compiler and its attendant services, so you get the same IntelliSense, you can share the same project files, etc.
Re:Visual Studio for Mac by Jaruzel on Monday November 14, 2016 @03:03AM (#12948233)
Visual Studio for Windows is mainly written in C# I believe.
Re:Visual Studio for Mac by moljacsharp on Monday November 14, 2016 @06:32AM (#12949080)
Nope.

Most of the UI was rewritten for VS2010 with WPF (XAML, DirectX acceleration), but lower/deeper parts are written in c++ and this makes porting "probelmatic" (MFC, win32.dll, kernel.dll to posix stuff).

MonoDevelop ~ Xamarin.Studio is written in C# (some plugins in F#) and this makes porting easier. That is the reason there was MonoDevelop version on Windows.