4 ms·

I've gotta say, honestly, I'm preferring Visual Studio Code over Atom simply due to the fact that it seems MUCH more stable and lightweight. Atom is very visual

I've gotta say, honestly, I'm preferring Visual Studio Code over Atom simply due to the fact that it seems MUCH more stable and lightweight. Atom is very visually appealing, and I'm a fan of the project, in general, but it constantly freezes up and crashes on me. I think I'll be sticking with VS Code & Sublime.

yulaow 11y ago
I have the same problem but VS code. I was using it for my node projects because it was very easy to use the debugger tool but it practically crashed (freezing the whole editor) 1/2 of the times so I reverted back to atom (that for me never crashed)... Can it be that we are both using old version of the editors (atom for you and vsCode for me)? Else it seems strange this difference of behaviors
- joshburgess 11y ago
  In the case of Atom, I don't think so, as I just updated to the recent version TODAY and had it freeze literally 3-4 times and fully crash once. I hear many people complain about similar issues with Atom. VSCode is in a much earlier development state (nowhere near Version 1.0 yet), but I've used it on Windows 8, Linux Mint, and Elementary OS without any issues whatsoever. shrug
euroclydon 11y ago
Visual Studio code needs to let me make CoreCLR executables on OSX and Linux, yesterday.
- ossreality 11y ago
  DNX does. Right now. You just want it to trigger 'dnu package' for you?
deleted 11y ago
[deleted]
bad_user 11y ago
Funny, as VS Code is based on Atom.
- wisew 11y ago
  VS Code is not based on Atom - it's built on Electron, the app framework Atom is also built on, and uses some of the same Node packages Atom developed.
  - bad_user 11y ago
    Electron was extracted from Atom and was originally named Atom Shell. I don't see your point.
    - wisew 11y ago
      Electron was also not extracted from Atom - it was always extracted as atom-shell. It was just rebranded as Electron. Atom ≠ atom-shell.
      - bad_user 11y ago
        Maybe we aren't speaking the same language. Here's what it says on electron.atom.io: "Initially developed for GitHub's Atom editor" So what are we talking about?
        rplnt 11y ago
        "for" does not equal "as part of".
- Touche 11y ago
  No it's not.
wisew 11y ago
In part, this is because VS Code is currently not extensible at all – there is no package ecosystem, and therefore no vector for users to possibly introduce instability / performance issues.
cageface 11y ago
FWIW I use Atom for hours every day to edit Ruby & JS code and it has never frozen up on me once. Earlier versions used to spin the CPU pretty hard at times but I haven't seen that for a while now either.

yulaow 11y ago

I have the same problem but VS code. I was using it for my node projects because it was very easy to use the debugger tool but it practically crashed (freezing the whole editor) 1/2 of the times so I reverted back to atom (that for me never crashed)... Can it be that we are both using old version of the editors (atom for you and vsCode for me)? Else it seems strange this difference of behaviors

joshburgess 11y ago
In the case of Atom, I don't think so, as I just updated to the recent version TODAY and had it freeze literally 3-4 times and fully crash once. I hear many people complain about similar issues with Atom. VSCode is in a much earlier development state (nowhere near Version 1.0 yet), but I've used it on Windows 8, Linux Mint, and Elementary OS without any issues whatsoever. shrug

euroclydon 11y ago

Visual Studio code needs to let me make CoreCLR executables on OSX and Linux, yesterday.

ossreality 11y ago
DNX does. Right now. You just want it to trigger 'dnu package' for you?

deleted 11y ago

[deleted]

bad_user 11y ago

Funny, as VS Code is based on Atom.

wisew 11y ago
VS Code is not based on Atom - it's built on Electron, the app framework Atom is also built on, and uses some of the same Node packages Atom developed.
- bad_user 11y ago
  Electron was extracted from Atom and was originally named Atom Shell. I don't see your point.
  - wisew 11y ago
    Electron was also not extracted from Atom - it was always extracted as atom-shell. It was just rebranded as Electron. Atom ≠ atom-shell.
    - bad_user 11y ago
      Maybe we aren't speaking the same language. Here's what it says on electron.atom.io: "Initially developed for GitHub's Atom editor" So what are we talking about?
      - rplnt 11y ago
        "for" does not equal "as part of".
Touche 11y ago
No it's not.

wisew 11y ago

In part, this is because VS Code is currently not extensible at all – there is no package ecosystem, and therefore no vector for users to possibly introduce instability / performance issues.

cageface 11y ago

FWIW I use Atom for hours every day to edit Ruby & JS code and it has never frozen up on me once. Earlier versions used to spin the CPU pretty hard at times but I haven't seen that for a while now either.