One concern I have is that they don't make it so feature rich that it becomes slow and overly complex - or at least be smart about which features to push out to extensions.
This isn't a consumer product, and it's not a "word processor". It's a tool for builders, so conventional wisdom about how great designers make the decisions instead of dumping them into preferences don't apply.
Great designers of tools like these figure out clever ways of helping users better customize their toolbox.
How does it compare in terms of memory usage w.r.t sublime ? I've a sublime project open for months that has never had any impact on system performance and it stays within 70MB RAM. Is VS Code even close ?
[1] https://hn.algolia.com/?query=visual%20studio%20code&sort=by...
They have detailed list of new features, with good GIF demos of new features. How can one not like a release post like that?
I'm glad it does. Each version bump, I come over the HN to check out what people have to say. It's an extremely useful tool to me and is developing rapidly. I'm using it, but I don't have as much time as I'd like to study it, so I glance through the comments to see if someone mentions something I'm not aware of that I should know.
I could get more about the product specifically from a good VSCode forum, but they don't seem to have one. A Github Issues page is not a proper user forum. (Maybe they have one now--as I said, I don't keep up as well as I'd like.)
But HN will tell me things about VSCode in a larger context, so I would probably want to keep reading comments here even if VSCode had a proper user forum.
At that point using find/replace or opening in sublime is a better option.
It became my second go-to editor, right after Sublime. Kudos to Microsoft for releasing as a free tool, and multi-platform.