# Visual Studio Code
**URL:** https://forum.kirupa.com/t/visual-studio-code/633178
**Category:** Uncategorized
**Created:** [May 12, 2015, 2:32pm UTC](https://forum.kirupa.com/t/visual-studio-code/633178 "2015-05-12T14:32:12Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@grimdeath](https://forum.kirupa.com/u/grimdeath)
#### Post date: [May 12, 2015, 2:32pm UTC](https://forum.kirupa.com/t/visual-studio-code/633178/1 "2015-05-12T14:32:12Z")
So Visual Studio Code is a lightweight text editor which is free and works on Windows, OSX and Linux it has some pretty cool/decent features (nodejs, intellisense, gulp, bower, git)
I can’t help but notice this is very similar to [Sublime Text](http://www.sublimetext.com/3) or [Atom](https://atom.io/) who knows it might be a fork of Atom, anyways just wanted to see what you guys think about this if you even heard about it.
---
### Author:  [@senocular](https://forum.kirupa.com/u/senocular)
#### Post date: [May 12, 2015, 5:07pm UTC](https://forum.kirupa.com/t/visual-studio-code/633178/2 "2015-05-12T17:07:01Z")
I think it is a fork of Atom… lemme see if I can verify…
[edit]
Yeep
---
### Author:  [@krilnon](https://forum.kirupa.com/u/krilnon)
#### Post date: [May 12, 2015, 6:25pm UTC](https://forum.kirupa.com/t/visual-studio-code/633178/3 "2015-05-12T18:25:04Z")
It’s interesting. Funny to see that most of the size of the app is the Chromium shell. (It’s less funny that the same is true for Atom, since Microsoft isn’t the one shipping it.)
Funny to see TypeScript syntax when you hover over identifiers to see type info. Not so funny to see a bunch of squiggly underlines in an HTML file that loads D3 and some other stuff over HTTP in script tags. I mean, I get that the editor’s not going to want to download those files, but it’s complaining about something that’s a super common pattern, especially if I’m just opening up Code to test it out quickly and don’t want to invest in figuring out its project structure.
---
### Author:  [@kirupa](https://forum.kirupa.com/u/kirupa)
#### Post date: [May 13, 2015, 7:15pm UTC](https://forum.kirupa.com/t/visual-studio-code/633178/4 "2015-05-13T19:15:31Z")
I’ve heard about its development for some time now, but I am still too much in love with either plain Atom with Live Preview (and a bunch of other packages) or Brackets with Live Preview.
😄
---
### Author:  [@senocular](https://forum.kirupa.com/u/senocular)
#### Post date: [June 24, 2015, 12:32pm UTC](https://forum.kirupa.com/t/visual-studio-code/633178/5 "2015-06-24T12:32:05Z")
Facebook has released their Atom-based editor (Nuclide) too:
> **[Building Nuclide, a unified developer experience](https://code.facebook.com/posts/397706937084869/)**
>
> Nuclide is a project designed to provide a unified developer experience for engineers whether they work on native iOS apps, on React and React Native code, or on Hack for our HHVM web server runtime.
---
### Author:  [@krilnon](https://forum.kirupa.com/u/krilnon)
#### Post date: [June 25, 2015, 3:27am UTC](https://forum.kirupa.com/t/visual-studio-code/633178/6 "2015-06-25T03:27:44Z")
Haha yeah, saw this. So much Atom these days! And it’s always seemingly using 1GB+ RAM… which is fine I guess but why does a text editor with ~10 open text files use 1/16 of the memory on the entire computer?
Avik works on related stuff now. I mean, projects sort of bundled into Nuclide.
---
### Author:  [@senocular](https://forum.kirupa.com/u/senocular)
#### Post date: [June 25, 2015, 3:58pm UTC](https://forum.kirupa.com/t/visual-studio-code/633178/7 "2015-06-25T15:58:10Z")
And not to be outdone by the recent release of Atom 1.0:
> **[Atom 1.0](http://blog.atom.io/2015/06/25/atom-1-0.html)**
>
> A hackable text editor for the 21st Century
And I’m guessing the text editor does very little with all that memory, but just happens to rely on a convoluted tech stack that does.
---
### Author:  [@krilnon](https://forum.kirupa.com/u/krilnon)
#### Post date: [July 15, 2015, 8:20am UTC](https://forum.kirupa.com/t/visual-studio-code/633178/8 "2015-07-15T08:20:45Z")
Thought about using TypeScript and VS Code for a recent project I had latitude on. Didn’t work out because it seemed like everything was relying on this one person’s 3rd-party type definition repo, and getting any type info required marking every import with something like:
`/// `
It just seems like… if I’ve hit the point where I’m writing _significant XML comments in JavaScript_ to enforce some type semantics, I’ve gone terribly off the rails.