4 ms·
I don't know how is it now, but I've used it for a couple of months for web dev on my mac and switched to Atom when noticed my cpu was 70%+ of usage all the tim
by gbaygon 8y ago
I don't know how is it now, but I've used it for a couple of months for web dev on my mac and switched to Atom when noticed my cpu was 70%+ of usage all the time. I suspected it was because of the typescript plugin, but honestly I don't care Atom doesn't do that and I'm happy with it.
- chrisabrams 8y agoInteresting I made the opposite switch for the exact same reason.
- deleted 8y ago[deleted]
- orf 8y agoI'd have at least spent 15 minutes working out what was causing it before taking the jump and switching editors?
- gbaygon 8y agoI had, but this was several version back, couldn't find any info of what was failing and also waited a major version update before doing the switch. Switching editors always causes stress. That's why it's hard to gain users back once you made a mistake on this (very competitive) field. I would only try VS Code again if Atom messes up, no matter what new micro site Microsoft PR puts online. Edit-to-add: with your downvote you are invited to explain why/if I'm wrong.