7 ms·

This editor is built on Atom.

by jordz 11y ago

Scarbutt 11y ago
Looks like it just uses Electron.
AdamTReineke 11y ago
From their docs: https://code.visualstudio.com/Docs https://code.visualstudio.com/Docs Architecturally, Visual Studio Code combines the best of web, native, and language-specific technologies. Using the GitHub Electron Shell, Code combines web technologies such as JavaScript and Node.js with the speed and flexibility of native apps. Code uses a newer, faster version of the same industrial-strength HTML-based editor that has powered the “Monaco” cloud editor, Internet Explorer's F12 Tools, and other projects. And Code uses a tools service architecture that enables it to use many of the same technologies that power Visual Studio, including Roslyn for .NET, TypeScript, the Visual Studio debugging engine, and more. In future previews, as we continue to evolve and refine this architecture, Visual Studio Code will include a public extensibility model that lets developers build and use plug-ins, and richly customize their edit-build-debug experience.
- MCRed 11y ago
  The Electron Shell was previously known as the Atom Shell. So part of it is Atom work.
  - tlianza 11y ago
    embraced and extended? [ducks]
    - lugg 11y ago
      I don't think they've extended it yet: $ /Applications/Visual\ Studio\ Code.app/Contents/MacOS/Atom .
  - AdamTReineke 11y ago
    Fair point. I wanted to clarify the difference since "built on Atom" has a different meaning to me than "using the GitHub Electron shell". The first sounds like an extension to Atom and the second sounds like a whole new app.
    - jordz 11y ago
      They started work on this before the Atom Shell was "Electron" and speaking to the team in Zurich before this was unveiled (about 3 months ago) they mentioned this was built on top of Atoms foundations. There is an Atom binary inside the package app and this is where my comment came from (:
deleted 11y ago
[deleted]
M8 11y ago
So it's crappy HTML and JS underneath? I was hoping for cross-platform WPF :(.
- pistle 11y ago
  Ahhh we can dream... sigh
- JustSomeNobody 11y ago
  WPF?! You cannot be serious.
  - WDCDev 11y ago
    WPF is, by far, the most pleasant and flexible thick client, windowing system out there. XAML is a bit verbose, but the binding capabilities combined with an open source MVVM framework like Caliburn allow you to build extremely flexible UIs. WPF also abstracts control behavior away from presentation and allows you to easily and quickly extend the base set of controls to do whatever you want to. After building multiple thick client applications using VB6, MFC, Swign, Winforms and WPF, WPF exceeds all of these, by far, in flexibility and maintainability.
    - jaked89 11y ago
      I find the binding part and MVVM stuff rubbish. For me, the real value is composition flexibility.
    - _random_ 11y ago
      Also <grid> (as a sane alternative to <div class="table">) where you can actually align stuff exactly the way you want.
      - nailer 11y ago
        You know about flex box right?
    - antonmaju 11y ago
DonHopkins 11y ago
Neato -- lots of JS code in: Visual Studio Code.app/Contents/Resources/app Try using it to view its own source code inside the app!
frik 11y ago
It seems this is the predecessor: Visual Studio Online (2013): http://weblogs.asp.net/jongalloway/a-quick-look-at-the-new-visual-studio-online-quot-monaco-quot-code-editor http://weblogs.asp.net/jongalloway/a-quick-look-at-the-new-v... (scroll down half way to see the screenshots and videos) So the idea and technology behind it predates Satya Nadella CEO appointment by at least 3 months.
- UK-AL 11y ago
  Visual Studio Online is basically TFS online. Think github + CI + Kanban board + Issue tracking online.
  - frik 11y ago
    It's more than that. Scroll half way down on my link above, check out the screenshots and video. Visual Studio Code is more like an offline version of Visual Studio Online (the editor part), 2 years later.
    - UK-AL 11y ago
      The editor is a tiny tiny tiny tiny part of VS Online.
      - frik 11y ago
        And exactly that "not so tiny" editor is the big part of Visual Studio Code. And it is not trivial at all - it's a very complex component to get right. The editor component comes from Switzerland and is called "monaco" and one of the main reasons why the "TypeScript" language exists and why ES6 looks as it looks today.
- zaphar 11y ago
  MS has always had great ideas and technology waiting in the wings. The problem was always they could never ship it. Nadella's contribution is to make it possible to ship this sort of thing. Shipping this under Ballmer would have been a miracle.
MCRed 11y ago
So is there any reason to use it instead of Atom? (assuming you're not developing with .net or C#)
- tdestan 11y ago
  If it supports any form of semantic completion (i.e. Intellisense) , that would be a reason. I'm still not sure from reading the article if that's the case, though.
homulilly 11y ago
Can't be entirely Atom since so far it actually seems pretty responsive.
- jevgeni 11y ago
  Oh, snap!

This editor is built on Atom.

by jordz 11y ago

This editor is built on Atom.

Scarbutt 11y ago

Looks like it just uses Electron.

AdamTReineke 11y ago

From their docs: https://code.visualstudio.com/Docs https://code.visualstudio.com/Docs Architecturally, Visual Studio Code combines the best of web, native, and language-specific technologies. Using the GitHub Electron Shell, Code combines web technologies such as JavaScript and Node.js with the speed and flexibility of native apps. Code uses a newer, faster version of the same industrial-strength HTML-based editor that has powered the “Monaco” cloud editor, Internet Explorer's F12 Tools, and other projects. And Code uses a tools service architecture that enables it to use many of the same technologies that power Visual Studio, including Roslyn for .NET, TypeScript, the Visual Studio debugging engine, and more. In future previews, as we continue to evolve and refine this architecture, Visual Studio Code will include a public extensibility model that lets developers build and use plug-ins, and richly customize their edit-build-debug experience.

MCRed 11y ago
The Electron Shell was previously known as the Atom Shell. So part of it is Atom work.
- tlianza 11y ago
  embraced and extended? [ducks]
  - lugg 11y ago
    I don't think they've extended it yet: $ /Applications/Visual\ Studio\ Code.app/Contents/MacOS/Atom .
- AdamTReineke 11y ago
  Fair point. I wanted to clarify the difference since "built on Atom" has a different meaning to me than "using the GitHub Electron shell". The first sounds like an extension to Atom and the second sounds like a whole new app.
  - jordz 11y ago
    They started work on this before the Atom Shell was "Electron" and speaking to the team in Zurich before this was unveiled (about 3 months ago) they mentioned this was built on top of Atoms foundations. There is an Atom binary inside the package app and this is where my comment came from (:

deleted 11y ago

[deleted]

M8 11y ago

So it's crappy HTML and JS underneath? I was hoping for cross-platform WPF :(.

pistle 11y ago
Ahhh we can dream... sigh
JustSomeNobody 11y ago
WPF?! You cannot be serious.
- WDCDev 11y ago
  WPF is, by far, the most pleasant and flexible thick client, windowing system out there. XAML is a bit verbose, but the binding capabilities combined with an open source MVVM framework like Caliburn allow you to build extremely flexible UIs. WPF also abstracts control behavior away from presentation and allows you to easily and quickly extend the base set of controls to do whatever you want to. After building multiple thick client applications using VB6, MFC, Swign, Winforms and WPF, WPF exceeds all of these, by far, in flexibility and maintainability.
  - jaked89 11y ago
    I find the binding part and MVVM stuff rubbish. For me, the real value is composition flexibility.
  - _random_ 11y ago
    Also <grid> (as a sane alternative to <div class="table">) where you can actually align stuff exactly the way you want.
    - nailer 11y ago
      You know about flex box right?
  - antonmaju 11y ago

DonHopkins 11y ago

Neato -- lots of JS code in: Visual Studio Code.app/Contents/Resources/app Try using it to view its own source code inside the app!

frik 11y ago

It seems this is the predecessor: Visual Studio Online (2013): http://weblogs.asp.net/jongalloway/a-quick-look-at-the-new-visual-studio-online-quot-monaco-quot-code-editor http://weblogs.asp.net/jongalloway/a-quick-look-at-the-new-v... (scroll down half way to see the screenshots and videos) So the idea and technology behind it predates Satya Nadella CEO appointment by at least 3 months.

UK-AL 11y ago
Visual Studio Online is basically TFS online. Think github + CI + Kanban board + Issue tracking online.
- frik 11y ago
  It's more than that. Scroll half way down on my link above, check out the screenshots and video. Visual Studio Code is more like an offline version of Visual Studio Online (the editor part), 2 years later.
  - UK-AL 11y ago
    The editor is a tiny tiny tiny tiny part of VS Online.
    - frik 11y ago
      And exactly that "not so tiny" editor is the big part of Visual Studio Code. And it is not trivial at all - it's a very complex component to get right. The editor component comes from Switzerland and is called "monaco" and one of the main reasons why the "TypeScript" language exists and why ES6 looks as it looks today.
zaphar 11y ago
MS has always had great ideas and technology waiting in the wings. The problem was always they could never ship it. Nadella's contribution is to make it possible to ship this sort of thing. Shipping this under Ballmer would have been a miracle.

MCRed 11y ago

So is there any reason to use it instead of Atom? (assuming you're not developing with .net or C#)

tdestan 11y ago
If it supports any form of semantic completion (i.e. Intellisense) , that would be a reason. I'm still not sure from reading the article if that's the case, though.

homulilly 11y ago

Can't be entirely Atom since so far it actually seems pretty responsive.

jevgeni 11y ago
Oh, snap!