The regular Visual Studio uses about the same amount of memory as VSCode while being an order of magnitude more complex and feature-rich.
VS Code Roadmap 2018
221–230 of 236 posts
Re: VS Code Roadmap 2018
#222Earlier quoted context omitted.
Vim can be really slow with too many plugins running.
I've also noticed that it's slow on Macs for some reason too. The same set of plugins don't seem to cause a slowdown on Linux.
That's very strange, it seems to be the case for both Vim and Neovim, and it doesn't depend on the terminal or shell I'm using. Is it just something inherent in the Mac environment then? I was always left scratching my head over the number of plug-ins people used, wondering how the program was even functional for them.
Re: VS Code Roadmap 2018
#223My main wish for VS Code is 'proper' multiple cursors (where by 'proper' I mean 'works the way I expect' which is the Sublime Text way). I fully understand that if you come from a world of 2D blocks (or regions) where you can select rectangles then VS Code's way of doing things makes sense but I am so used to having multiple identical cursors and being able to swipe vertical lines through tables of text or more often…
Hi, I'm a VS Code developer.
Can you please open a new issue and describe "as you would to a five year old" what's not working as expected.
Even from reading this comment thread I simply don't get it, so it might be something very easy to fix, once I do understand what it's about.
Thank you for your patience! :)
Re: VS Code Roadmap 2018
#224My main wish for VS Code is 'proper' multiple cursors (where by 'proper' I mean 'works the way I expect' which is the Sublime Text way). I fully understand that if you come from a world of 2D blocks (or regions) where you can select rectangles then VS Code's way of doing things makes sense but I am so used to having multiple identical cursors and being able to swipe vertical lines through tables of text or more often…
Hi, I'm a VS Code developer. Can you please open a new issue and describe "as you would to a five year old" what's not working as expected. Even from reading this comment thread I simply don't get it, so it might be something very easy to fix, once I do understand what it's about. Thank you for your patience! :)
Whoop! Would love to—thanks for your time :)
Re: VS Code Roadmap 2018
#225Earlier quoted context omitted.
"Single-site browser", or "site specific browser". Basically a very thin wrapper over the systems web view.
Me, too. For instance, I use a site-specific browser for: - CircleCI - GitHub - JIRA (blecch, but I have to use it...) - AWS - Google Docs (for work, and the rare personal use of Google stuff can just happen in one of the general browsers I am using) ...and others. The OS does a much better job of partitioning windows and groups of windows than a browser typically does. You can easily keep switch between groups of wi…
See MacPin (https://github.com/kfix/MacPin/tree/swift2.3) and FluidApp (http://fluidapp.com/).
And yes, Chrome, at least on windows, has an `--app` switch.
Re: VS Code Roadmap 2018
#226Earlier quoted context omitted.
For some reason people still consider startup time a metric worth paying attention to
Engineers like to optimize everything, including how they use their time. If you've got something in your head that you want to fix or write, you want to spend time doing just that, not staring at your screen waiting and maybe losing some of your mental model.
That’s why I never close the project(s) I’m working on. So my startup time is instantaneous
Re: VS Code Roadmap 2018
#227Earlier quoted context omitted.
For some reason people still consider startup time a metric worth paying attention to
I use VS Code most of the time, but the reason I always use Notepad for taking quick notes _is_ the startup time of VS Code. If they improved it, I'd be using it for both. It is an important metric for some.
I work in IntelliJ IDEA whise startup times are horrible. However, since I always work on a set of projects, I never close them, so, essentially, startup time is 0.
Also, IDEA has scratch files for quick notes available through a shortcut (I guess VS Code might have a similar plugin), so startup tome isn’t an issue either.
Re: VS Code Roadmap 2018
#228Earlier quoted context omitted.
For me ”marrying to an editor” is mostly about muscle memory. Onve you know all tje shortcuts, you are much more productive
> all the shortcuts You are clearly not an Emacs user.
I was, for a few years. There are numerous shortcuts you end up using.
Re: VS Code Roadmap 2018
#229Earlier quoted context omitted.
Sure, Sublime is practically instant whereas VSCode takes... maybe slightly more than half a second on my machine. It’s noticeable but is it really that much of an issue?
Opening big files, opening lots of files, doing search and replace in open files, and my favourite, use thousands of parallel cursors to thousands of simultaneous edits in a single file, they are all noticeable slower in VSCode. Damn, I love me them multiple cursors.
Never done thousands (wtf are you doing??) but I’ve done dozens and it’s been instant in VSCode.
Define large too - several mb? Or several 100?
Maybe you’re just an outlier?
Re: VS Code Roadmap 2018
#230Vscode + Typescript magic