3 ms·
Just tried VS Code, because I was curious... It seems to be using around 230MB of ram, and almost no CPU with a single file open... I was surprised how much bet
by tracker1 11y ago
Just tried VS Code, because I was curious... It seems to be using around 230MB of ram, and almost no CPU with a single file open... I was surprised how much better it worked compared to some of the other browser/nwjs/electron based editors. It's become my daily driver.
- leejoramo 11y agoI am watching VS Code too. At the moment, Code's eco-system of add-on packages is missing too many tools I would want on a daily basis. However, I like the strong progress and road map, I could see Code being my go-to editor in the next year. Actually, it has been a few months since I last checked on VS Code, I guess I should give it a spin again.
- happyhowler 11y agoJust curious, what kinds of tools are essential for you to switch?
- leejoramo 11y agoI use many of the features of Anaconda Python IDE. I know that better Python integration is high on the list priorities for VS Code, so I think this may happened. http://damnwidget.github.io/anaconda/# http://damnwidget.github.io/anaconda/#
- fuzzywalrus 11y agoI tested out VS Code, seemed nice enough. Hopefully it'll get the tight integration with Git that Atom has. I have a love / hate relationship with Atom right now.
- spleeder 11y agoVS Code has much better git integration than Atom will ever have out of the box because Atom does not want to compete with GitHub for Desktop.
- brazzledazzle 11y agoIf true it's somewhat disheartening to see that newer companies are still carrying on the tradition of limiting a product (not that Atom is a "product" per se) in favor of promoting another one. I think there's a name coined for it but I can't recall it at the moment.