4 ms·
I also just got access to the beta. It works very seamlessly. You can install all the VSCode extensions you want. It came preinstalled with some Python 3.8 ven
by albertzeyer 6y ago
I also just got access to the beta. It works very seamlessly. You can install all the VSCode extensions you want.
It came preinstalled with some Python 3.8 venv. The venv was put into the Git repo root directory, which is a bit strange, as I first needed to modify my gitignore to ignore that.
Git push directly from the VSCode menu directly worked and pushed the change back to GitHub, without further setup.
I did not expect that I get a full virtual machine, but it seems so. I edited some Latex project, and pdflatex was missing, so I did `sudo apt install texlive-full`, it installed 4GB of packages, and then all worked fine.
I also edited some TensorFlow stuff, and `pip3 install tensorflow` also just worked.
The side preview (eg. for markdown or Latex) somehow is broken. It stays blank. However, e.g. you can open the Latex PDF preview in a new browser window, which works.
The speed just felt native. There was no latency. It feels exactly like native VSCode.
I very much like it. I guess the side preview will get fixed soon. I will probably use it for a couple of smaller projects, of different kinds, like Latex, Markdown notes, smaller Python stuff, or other smaller code projects where VSCode is fine.
Otherwise, for e.g. Python, I still prefer PyCharm, which has far superior code browsing and auto-completion. Codespaces with PyCharm would be really nice! Or maybe VSCode can improve on that. Or maybe VSCode can even reuse the language server from VSCode. Or at least the inspections. I think this part is open source, right?
- dlkmp 6y agoFrom the blog post I understand that my vscode configuration is somehow stored within my browser, not connected to my github account. Is it also stored per project or globally? Because either choice brings its own problems. I want the vim plugin to behave the same on all instances but language-specific plugins or similar only make sense in the context of a specific project. How does this work currently?
- albertzeyer 6y agoIt stores settings just as usual in .vscode/settings.json in your project. (I usually have .vscode in my .gitignore, but maybe it make sense to include it in the repo.) Additionally, there is some "Settings-Sync" feature, which I have not really explored yet. Maybe this is global for all instances. Btw, the startup time of the codespace VM is a bit annoying. It takes approx 30-60 seconds when it was inactive. And it get automatically suspended after 30 minutes of inactivity.
- WorldMaker 6y agoIn addition to project local .vscode/settings.json and the still Beta Settings Sync, it should also pick up your user settings if you set up a dotfiles repository.