Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub Copilot App

github.com

Post reply on HN
Print view View original

11–20 of 83 posts

Re: GitHub Copilot App

#11

Post by Anon1096 »

matthew_hre wrote: post #3

Unrelated to the feature itself, but remember a few months ago when someone posted Github's beta feature for stacked PRs, and a ton of people slammed them for releasing a seemingly vibe-coded site? To quote Mitchell Hashimoto, "One of the most requested GitHub features in years and the website looks like it was designed by someone 9 years into a 2 year community college program."[1] When opening the posted link, my f…

Target market for stacked PRs are ICs who don't have much decision making power and let's be real do not care too much about the look and feel of a "launch site" for the feature. It's also something few if anyone is making a purchasing decision over.

Target market for copilot includes people with actual purchasing power and also many new users where this is an actual make or break feature. So this is worth the investment into design while stacked PRs is questionable. I actually question why they bothered with anything more than a blog post at all for stacked PRs (looking at the post it doesn't seem like too too much more than a blog post though).

Re: GitHub Copilot App

#12

Post by jollyllama »

panos_news wrote: post #6
2001zhaozhao wrote: post #4

It's kind of interesting that everyone is going for the desktop app format now. These desktop agentic coding tools are a large UX step up from the CLIs, but I still think the future is going to be remote development as the coding agents start running for hours at a time. Building a desktop app seems short-sighted as it would just lock them out of the remote option completely.

I think their goal is to lock you into their ecosystem instead of using your IDE

They want all your data. A browser doesn't get them that as well.

Re: GitHub Copilot App

#13

Post by infraredshift »

matthew_hre wrote: post #3

Unrelated to the feature itself, but remember a few months ago when someone posted Github's beta feature for stacked PRs, and a ton of people slammed them for releasing a seemingly vibe-coded site? To quote Mitchell Hashimoto, "One of the most requested GitHub features in years and the website looks like it was designed by someone 9 years into a 2 year community college program."[1] When opening the posted link, my f…

[dead]

Re: GitHub Copilot App

#15

Post by kirtivr »

roetlich wrote: post #2

Who would have thought that git worktree is the technology of the year 2026?

Yeah, when you had multiple agents working on the same machine, branch isolation was no longer sufficient.

A repository folder can only be on one branch at a time.

A worktree is basically equivalent to a cp -R + git branch, which allows this new workflow to occur.

I loved this particular historical insight as to why `git worktree` was added in 2015:

Before worktrees, kernel devs faced a major inconvenience when switching contexts, e.g., stopping feature work to fix an urgent bug on a release branch.

Running git stash and switching branches alters timestamps on thousands of files.

This forces `make` to perform a full re-compile, which can take up to an hour on large kernels.

Re: GitHub Copilot App

#17

Post by hootz »

2001zhaozhao wrote: post #4

It's kind of interesting that everyone is going for the desktop app format now. These desktop agentic coding tools are a large UX step up from the CLIs, but I still think the future is going to be remote development as the coding agents start running for hours at a time. Building a desktop app seems short-sighted as it would just lock them out of the remote option completely.

The desktop app can become a client for their remote cloud agent solution (yuck).

Re: GitHub Copilot App

#20

Post by 8n4vidtmkvmk »

2001zhaozhao wrote: post #4

It's kind of interesting that everyone is going for the desktop app format now. These desktop agentic coding tools are a large UX step up from the CLIs, but I still think the future is going to be remote development as the coding agents start running for hours at a time. Building a desktop app seems short-sighted as it would just lock them out of the remote option completely.

Doesn't lock you out at all. Codex already had a companion app for mobile so you can send prompts to your desktop app while you go about your business. The infrastructure is there. Server might move from your desktop to cloud at some point but not much changes. Still needs somewhere to run.
Post reply on HN