11–20 of 704 posts
I'd love to use Codespaces or a self hosted alternative so that I don't need to carry around a heavy i7 laptop.
Being able to develop in the cloud from a browser opens up the possibility to develop from a thin Chromebook.
env portability/consistency/using prebuilds as an example could have been done with in house CD/vagrant/packer ~10y ago. This post doesn't focus specifically on that, and there are additional benefits to the approach taken, but the notion that local dev is incompatible with these types of technologies is a consistent background theme in the writing
also, referring to emacs as non graphical and 'shell based' is a bit off to say the least.
Unpopular opinion with a lot of my peers, but "fragile local dev environment" is usually a sign of an unwieldy, tightly coupled codebase with a lot of parts, scripts, etc. Trying to hide that complexity with docker or codespaces, etc is just a bandaid in many cases vs dealing with the root issues.
The future is long term probably in the web, I'm just not sure we are there yet.
I would quit so fast if my company forced me to use a web IDE.
I'm currently working on a huge codebase that takes forever to compile. I'd love to use Codespaces or a self hosted alternative so that I don't need to carry around a heavy i7 laptop. Being able to develop in the cloud from a browser opens up the possibility to develop from a thin Chromebook.
Unpopular opinion with a lot of my peers, but "fragile local dev environment" is usually a sign of an unwieldy, tightly coupled codebase with a lot of parts, scripts, etc. Trying to hide that complexity with docker or codespaces, etc is just a bandaid in many cases vs dealing with the root issues.
This has not been my experience. First, I work on lots of code bases and this is where a lot of the brittleness comes from. They don’t use the same versions of the same things. Second, C dependencies are a giant pain in the ass when you add the first problem above.
locked-in to visual studio code? no thanks
I would quit so fast if my company forced me to use a web IDE.
The article describes using pretty much any IDE, so they are just offloading the setup and running of the development environment to the cloud while letting you run your preferred IDE locally.
locked-in to visual studio code? no thanks
The article mentions supporting vim and emac, which probably means any editor can be supported. Visual Studio Code is great. It’s the primary tool GitHub.com engineers use to interface with codespaces. But asking our Vim and Emacs users to commit to a graphical editor is less great. If Codespaces was our future, we had to bring everyone along. Happily, we could support our shell-based colleagues through a simple upda…
I read that as you can ssh in and run a terminal-based editor, but that doesn't seem to offer much support for people looking to edit in NEdit or Intellij or Atom or Sublime or whatever else. Maybe some of those could be supported by forwarding an XSession out of the image, but that's going to suck hard for people on macOS whose editor is now the Linux/X version, with all of the attendant mismatch.