The big draw for me is working on the iPad. If you attach the keyboard it becomes a pretty awesome 'do anything' device, now that you can code on it as well. Can't build native apps yet, but seems like a future opportunity. Web apps / PWA development works great, I can just have the app running in a hovering window / on a quarter of the screen.
First Impressions of GitHub Codespaces
31–40 of 97 posts
Re: First Impressions of GitHub Codespaces
#32Earlier quoted context omitted.
> I’ve been spending a lot of time getting Windows Subsystem for Linux working I wouldn't spend a minute on it. Why bother with such an abomination when you can just use Linux the way it is intended to be used with less hassle and corporate superstructure that you most likely will never need.
Well if you're actually asking... I do it so I can use Windows tools like Unity (Editor just runs the best on Windows) and good graphics drivers, as well as having access to bash and linux tooling.
Wasn't Unity a Mac exclusive tool to start out? I know they have support for Windows at this point, and would understand if they've refocused on Windows since then.
Re: First Impressions of GitHub Codespaces
#33It 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?
Re: First Impressions of GitHub Codespaces
#34Earlier quoted context omitted.
I respect developers who make that work, but the development experience over SSH (vim, etc) is never as good as local development. You can't use vs code. You have to deal with lag delaying keystrokes. If you download a file and want to copy it into your dev environment you need to SCP it over. If you want to test a network service its nontrivial to point your local browser at the remote machine. If you sleep your lap…
> vs code check coc.vim, uses vsc's native LSP, 99% of LSP's features > delaying keystrokes I have 16ms latency as my 60hz screen does and def less latency than a local vscode just use a vps close to where you are
Re: First Impressions of GitHub Codespaces
#35I 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…
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?
Re: First Impressions of GitHub Codespaces
#36Re: First Impressions of GitHub Codespaces
#37Earlier quoted context omitted.
Well if you're actually asking... I do it so I can use Windows tools like Unity (Editor just runs the best on Windows) and good graphics drivers, as well as having access to bash and linux tooling.
> so I can use Windows tools like Unity (Editor just runs the best on Windows) Wasn't Unity a Mac exclusive tool to start out? I know they have support for Windows at this point, and would understand if they've refocused on Windows since then.
Also a lot of useful 3d content creation software is Windows only, or only supports CUDA acceleration, so implicitly rules out Mac from being a first class citizen (e.g. substance painter)
Obviously not every game is the same, or needs fancy tooling. But Windows feels like it just works for game dev.
Re: First Impressions of GitHub Codespaces
#38Re: First Impressions of GitHub Codespaces
#39I've been using an iPad Pro as a laptop replacement for the past year and Codespaces makes it a pretty viable development machine. I'd been mulling over switching back to a laptop, but I'll probably stick to the iPad for now.
Before I was using Blink shell to ssh into my desktop and run Emacs. Not really ideal for me since I mainly use VS Code on my desktop (which is my main computer) and hardly touch Emacs anymore.
Re: First Impressions of GitHub Codespaces
#40I'm pretty excited about what Codespaces is going to bring to the table. I can already see a lot of good use cases. I've been using an iPad Pro as a laptop replacement for the past year and Codespaces makes it a pretty viable development machine. I'd been mulling over switching back to a laptop, but I'll probably stick to the iPad for now. Before I was using Blink shell to ssh into my desktop and run Emacs. Not reall…