Live data from Hacker News

GitHub’s engineering team has moved to Codespaces

github.blog

241–250 of 704 posts

Re: GitHub’s engineering team has moved to Codespaces

#241
I feel like all of the problems in the blogpost are solvable without moving everyone to this crazy web development environment. To quote one of the proponents:

> I do solemnly swear that never again will my CPU have to compile ruby from source.

...yeah, why was that even happening? Why not distribute pre-built artifacts? I feel like the whole docker ecosystem only exists because people forgot how to distribute software and/or python/ruby and friends make deployment so hard.

Re: GitHub’s engineering team has moved to Codespaces

#242
post #95

Has anyone built a product that can beat Rubymine's code navigation capabilities? I can navigate to any internal or dependency definition, out of the box.

I find RubyMine to be sluggish, and I stick with SublimeText and a set of terminals. However, I was trying to debug a plugin of a plugin of a gem, and installed it again to see if it would help. I found the problem in about 5 minutes because of this navigation. Credit where due; it was pretty awesome.

Agree - I find other editors much more responsive.

But when I need to learn or explore a really large code base in Ruby, I haven't found anything better.

Re: GitHub’s engineering team has moved to Codespaces

#243
I've developed on a remote server for about 8 years now. It started when I was a contractor and my machine was simply too slow to run the project I was assigned. I did not have the money for a new laptop, but I could afford the ~55/month for a dedicated server with 32GB and 4cores. I have worked that way ever since. I've been fortunate enough to work at companies that run their own VM infrastructure which allow me to work this way. And as someone who likes to work in different places, like the park, being able to download docker images while on a Hotspot and it not go through my data plan is amazing.

Re: GitHub’s engineering team has moved to Codespaces

#244

Somehow I can see some companies using this to spy on their employees and "measure" how productive they are, and how their timesheets reports match.

This is 100% where the tools-in-the-cloud thing is going. It's going to be a major selling point for a lot of buyers (companies).

Re: GitHub’s engineering team has moved to Codespaces

#245
post #198

Earlier quoted context omitted.

https://en.m.wikipedia.org/wiki/Embrace,_extend,_and_extingu...

What are they embracing, how are they extending it, and how do they plan to extinguish it? My understanding of EEE is that it involves taking some competitive product/standard, making a cool MS version of it, and then killing off the standard version - e.g. implementing a barely sufficient POSIX layer on Windows, getting customers who have "POSIX" as a purchasing requirement to switch, and then getting them onto the…

It's a slightly different flavor of the same thing.

VS Code is an amazing tool that's getting huge adoption because of how awesome it is, and how open source and community centric it is, etc. They've gotten a lot of mindshare and dev love, that's the embrace bit.

The next step is the set of closed source addons. Have you noticed that a lot of the new VS Code features are now in addons that are under a different license. This includes the new remote dev and python tooling. Still free to use and awesome tools, of course, but fully under MS exclusive and controlled. That's the extend.

I don't know what the longer-term plan is. I'm hoping that it won't lead to an extinguish. But if that's what they want, then they could e.g. cripple the open source version, moving all their dev effort into a closed-source, Azure/Github only web environment. Who knows?

Re: GitHub’s engineering team has moved to Codespaces

#247

Ugh, now not only you don't own your code ( ahem copilot cough ) you also don't own the tools to develop code. The direction the web is taking is worrisome. The issue is not so much senior devs, but new devs. If they start off with things like that, there' so much magic under the hood, they won't understand how anything works. They don't understand they don't own shit until it's too late. I remember when I first saw…

The same thing was said about every programming abstraction to ever be introduced. How do we expect people to build memory-efficient applications when they become reliant on a garbage collector?

I'd argue that it always held true to a certain extent. You don't necessarily need the underlying knowledge to be an efficient programmer in Python, but knowing C or Assembly certainly gives you an edge when it comes to, well, edge cases.

And it isn't all about efficiency. Programming and CS is such a major part of my life, that I want to know the deeper parts, and I want others to understand it too. Programmers who do not seek that knowledge I unjustly judge for it.

Re: GitHub’s engineering team has moved to Codespaces

#248

Earlier quoted context omitted.

> And things like the Rails monolith that GitHub's main service is, have a tendency of being rude to a dev's laptop FUD. Everything is neatly handled by rvm (or rbenv) and bundler. You can even use gemsets if you want to be really anal about it. It all goes in version-controlled user directories. I keep my main Mac machine, my work Windows machine, and the production Linux boxes all running the same versioned stack j…

What do you mean FUD? Maybe you've got your own way of doing things that works well so far for you with your current projects, but a ton of people don't live with the same experience, and when they do reach a comfortable spot, it's only comfortable until they move to a new set of projects or company.

I'm saying that, while a top-tier, software-as-a-service company might have a development environment that is hard to bootstrap -- because of all the ancillary things that run alongside the "monolith" -- your generalization that "Rails" makes a mess of a development machine is FUD. The Ruby/Rails part of this equation is not the issue. As always, YMMV and TACMA.

Re: GitHub’s engineering team has moved to Codespaces

#249
I’m using a homebrew version of this — I built a powerful linux machine that i keep at home and I connect to via VS Code remote thing. It is very stable at this point, I’m very happy with this setup. I have a light laptop that is basically a thin client and I do coding on a 16 core computer that i can access from anywhere where there’s internet. Port forwarding works great too in VS Code. I use tailscale for networking so that’s also been nice, no need to mess with vpns or anything like that.

Re: GitHub’s engineering team has moved to Codespaces

#250

Ugh, now not only you don't own your code ( ahem copilot cough ) you also don't own the tools to develop code. The direction the web is taking is worrisome. The issue is not so much senior devs, but new devs. If they start off with things like that, there' so much magic under the hood, they won't understand how anything works. They don't understand they don't own shit until it's too late. I remember when I first saw…

Why should you own your code or your device?

Why should you trust your computer?

Why should your career be safe?

People are fungible resources to be used when convenient and agreeable. Say or do the wrong thing, or have your utility dip below a threshold, and you can be removed.

It's happening.

Post reply on HN