I would quit so fast if my company forced me to use a web IDE.
I am wary of requiring an internet connection in order to develop, but there seem to be more and more advantages to using something like Codespaces. 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.
GitHub’s engineering team has moved to Codespaces
81–90 of 704 posts
Re: GitHub’s engineering team has moved to Codespaces
#82Earlier quoted context omitted.
GitHub isn't forcing anybody to use a web IDE. The most broadly used access interface is VSCode. Then there are heretics like me who choose to ssh in so we can use Vim. This is described in the article.
Do you have to drag your .vimrc and plugins along every time you set up a new code space? My vim setup is pretty bespoke, it would be annoying to have to set that up every time.
https://docs.github.com/en/codespaces/customizing-your-codes...
I also have a very bespoke dotfiles config that predates Codespaces (https://github.com/wincent/wincent), so I made a thin wrapper around it that makes it work (https://github.com/wincent/dotfiles). For people with less complicated set-ups (ie. basically the entire universe), it is pretty straightforward.
Re: GitHub’s engineering team has moved to Codespaces
#83Is the direction in which all software development is heading?
We used to write COBOL using thin client on mainframes. Then we moved to development locally.
Re: GitHub’s engineering team has moved to Codespaces
#84I would quit so fast if my company forced me to use a web IDE.
I would be happy to let go of an employee who bank their employment on the preference of toolings. Hear me out: Toolings are, like the name suggests, a means to an end. If a web IDE is fast, works reasonably, and can continue improve itself. And the learning curve is friendly to engineers with different background and experience. Everyone should be comfortable to be nudged to use it. And if the tool additionally is a…
*it's always engineers making these statements or I only know engineers
Re: GitHub’s engineering team has moved to Codespaces
#85Just a couple of years ago some kid gained access to every repo on github. Now githubs code is going to be developed on an online platform, which works by sharing code others have uploaded. I have a feeling that this is not a good recipe.
Very curious to know more about this. What exactly are you talking about? Closest thing I could find is this[0], but you said "couple of years ago".
[0] https://www.zdnet.com/article/hacker-gains-access-to-a-small...
Re: GitHub’s engineering team has moved to Codespaces
#86Earlier quoted context omitted.
I would be happy to let go of an employee who bank their employment on the preference of toolings. Hear me out: Toolings are, like the name suggests, a means to an end. If a web IDE is fast, works reasonably, and can continue improve itself. And the learning curve is friendly to engineers with different background and experience. Everyone should be comfortable to be nudged to use it. And if the tool additionally is a…
I'd absolutely never work with someone so arrogant (and, for lack of a more polite word, dumb, as you). When I work for someone, I do the work they ask me and in return they pay me AND I get to learn something. For my learning process, I need the work part to be over fast. And that means I need to use stuff that I works best for me. I also need to be able to be able to fulfill my potential and spend time doing actual…
Re: GitHub’s engineering team has moved to Codespaces
#87I would quit so fast if my company forced me to use a web IDE.
Note that they mainly use VS Code and also support vim and emacs.
Re: GitHub’s engineering team has moved to Codespaces
#88Re: GitHub’s engineering team has moved to Codespaces
#89I was curious about the cost. The pricing and compute resources just about correspond to an Azure A series instances, but the ram corresponds better to the v2 series, which is cheaper than v1. I wonder if they're upcharging for v2 machines.
These are also the costs for Teams/Enterprise (who would be willing to pay more); I wonder if they'll release a cheaper/free SKU for individual users.
This might be very resource intensive though.
Re: GitHub’s engineering team has moved to Codespaces
#90On GitHub, that instance type is $2.88/hour or $2,073 monthly per developer for a single instance.
(Granted, that's running 24/7 but still - wow, that's expensive for a single instance)