Live data from Hacker News

GitHub’s engineering team has moved to Codespaces

github.blog

261–270 of 704 posts

Re: GitHub’s engineering team has moved to Codespaces

#261
post #251

Hello! Blog post author here. Wanted to quickly comment on how we support offline folks or those working on an unstable connection! The short version: we publish a container image into the GitHub Container Registry that closely tracks github/github’s devcontainer image. Folks can pull and use locally with VSCode remote containers or run directly in Docker. The github/github checkout is local in this case and mounted…

So I can use the same workflow with codespaces connected to a local container? Is that documented somewhere?

Re: GitHub’s engineering team has moved to Codespaces

#262

Earlier quoted context omitted.

I've never seen a company collapse because their garbage collector posted an Our Incredible Journey™ blog post and then shut down a week later. I have seen multiple companies collapse because the proprietary Backend-as-a-Service they built their sand castle on top of pulled a vanishing act, however.

What’s an example of a company collapsing in that way? I actually can’t think of any.

Any company built on a 3rd party API. Many examples on twitter.

Re: GitHub’s engineering team has moved to Codespaces

#263
post #259

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…

If you work from a park how do you manage your latency/connectivity to a remote server? It must get annoying fast when a pigeon flies over causing your hotspot to cut out.

He could use something like GNU screen, or tmux, or his server could use something like XRDP or even RDP to continue when his connection goes out.

Re: GitHub’s engineering team has moved to Codespaces

#264
post #208

Earlier quoted context omitted.

There's plenty of companies that wasted a ton of resources trying to roll their own version of things that should be services. Remember when Uber built their own chat solution? [0] > With operations in over 620 cities, it was paramount for us to identify a chat solution that would enable Uber employees to reliably communicate on desktop and mobile regardless of where they were in the world. Did Uber really need their…

I see your point. But at Uber's scale I can see the business need for a custom chat app. Most third party chat apps are bloated, both the cheap and expensive ones. Plus there's the need for custom integrations.

I used to work at a large bank and they operated perfectly fine with Window's messenger. As does every other bank in the US, despite having tens if not hundred of thousands of employees. Some things require more specialized features like trade tickets (which Bloomberg does), but for chatting, you're not gonna be able to build a better solution than already exists. And if you can, then you should spin that off into its own business like Goldman did with Symphony [0]

The nice thing about being a client is that they support all this stuff and it gets better over time. Also something like Slack is absurdly cheap compared to the usefulness and productivity it provides.

[0] https://en.wikipedia.org/wiki/Symphony_Communication

Re: GitHub’s engineering team has moved to Codespaces

#265
post #259

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…

If you work from a park how do you manage your latency/connectivity to a remote server? It must get annoying fast when a pigeon flies over causing your hotspot to cut out.

[deleted]

Re: GitHub’s engineering team has moved to Codespaces

#266

It sounds like this use case is for developer's who buy laptops expecting them to act like desktops and then realize their mistake. Maybe the cheaper, simpler, option is just to buy a performant desktop for less $$$ than has wall current and the space for RAM and heat dissipation.

I forked out a silly amount of money on a laptop last year as I assumed I'd be working abroad for a while. I knew developing on a laptop would suck and I was proven right. I don't know why some people prefer it. (The M1s may change that today)

Re: GitHub’s engineering team has moved to Codespaces

#267
post #259

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…

If you work from a park how do you manage your latency/connectivity to a remote server? It must get annoying fast when a pigeon flies over causing your hotspot to cut out.

I think the point is that a small random drop in latency affects the local connection, but not the remote server. So, if your SSH connection is a little flakey for a minute, that’s fine. The remote server is itself stable. It is also likely connected to a much bigger pipe, so pulling in a remote container is much faster than if you were doing the same thing from your laptop in the park.

If you’re worried about your SSH connection being stable, mosh is another option.

Re: GitHub’s engineering team has moved to Codespaces

#268
post #224

Earlier quoted context omitted.

It's funny because we told people not to trust big companies, they tell us we are paranoid, they do it, they pay the price for it, then they say we were right, then they do it again. MS changed. Google changed. Apple changed. Why do one expect github to never turn evil ? Haven't learned enough from history ? Don't let them control your entire stack! Don't let anybody control the entire of anything. There is a differe…

It's over once we don't have control of the compilers. Look at the iPhone.

iPhone is the direction everything is trending.

Fight this bullshit. Call your pro-breakup / anti-trust representatives and give them the reasons this is bad for you and your career. Tell them the narrative and give them ammunition to fight this.

Google, Amazon, Apple, and now Microsoft deserve regulations and/or dissolution.

Re: GitHub’s engineering team has moved to Codespaces

#269
I used AWS Cloud9 for years now and for half a year I'm using Codespaces.

I don't like the one IDE per repo model, but I like VSCode more than Cloud9.

It would just be cooler if it would still work when I go offline. Working in a train is simply no fun.

Re: GitHub’s engineering team has moved to Codespaces

#270
post #259

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…

If you work from a park how do you manage your latency/connectivity to a remote server? It must get annoying fast when a pigeon flies over causing your hotspot to cut out.

Files are stored in memory locally so there’s no network trip when editing, only on save, and it’s kilobytes per edit in the worst case
Post reply on HN