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

GitHub Introduces Copilot Extensions

github.blog

Post reply on HN
Print view View original

1–9 of 9 posts

Re: GitHub Introduces Copilot Extensions

#2

Post by bnchrch »

This type of vertical integration must have Amazon a little worried.

For example, if Microsoft took a chapter from Apples (anticompetitive) playbook with Spotify, They could always make Azure Extensions N features ahead of equivalent AWS Extensions.

The productivity gains vscode devs would have by using Azure would always be more than AWS, and the cycle of user lock in would march forward.

Re: GitHub Introduces Copilot Extensions

#3

Post by ralph84 »

bnchrch wrote: post #2

This type of vertical integration must have Amazon a little worried. For example, if Microsoft took a chapter from Apples (anticompetitive) playbook with Spotify, They could always make Azure Extensions N features ahead of equivalent AWS Extensions. The productivity gains vscode devs would have by using Azure would always be more than AWS, and the cycle of user lock in would march forward.

It’s surprising that Amazon hasn’t bought Atlassian or GitLab and Google hasn’t bought the other one. Maybe owning a developer platform is core to Microsoft’s DNA in a way that it could never be for a retailer or advertising company, but the synergies of having a developer platform to complement your cloud platform are obvious.

Re: GitHub Introduces Copilot Extensions

#4

Post by cmpalmer52 »

They need one for .NET MAUI. Copilot does a poor job helping with our port from Xamarin. “Maui is in pre-release at the time of training, so check the official documentation.” I’ve seen that several times on CoPilot and the JetBrains Rider AI.

Re: GitHub Introduces Copilot Extensions

#5

Post by mdaniel »

ralph84 wrote: post #3
bnchrch wrote: post #2

This type of vertical integration must have Amazon a little worried. For example, if Microsoft took a chapter from Apples (anticompetitive) playbook with Spotify, They could always make Azure Extensions N features ahead of equivalent AWS Extensions. The productivity gains vscode devs would have by using Azure would always be more than AWS, and the cycle of user lock in would march forward.

It’s surprising that Amazon hasn’t bought Atlassian or GitLab and Google hasn’t bought the other one. Maybe owning a developer platform is core to Microsoft’s DNA in a way that it could never be for a retailer or advertising company, but the synergies of having a developer platform to complement your cloud platform are obvious.

> It’s surprising that Amazon hasn’t bought Atlassian or GitLab and Google hasn’t bought the other one

GitLab and Google would have much better "synergy" since GL already runs on GCP. The ruby may be a culture clash, but I wouldn't put it past Google to have some tooling to help GL straighten out their ruby mess

Secretly, though, I want Google to buy Atlassian just to send it to KilledByGoogle

Re: GitHub Introduces Copilot Extensions

#6

Post by beretguy »

mdaniel wrote: post #5
ralph84 wrote: post #3

Earlier quoted context omitted.

It’s surprising that Amazon hasn’t bought Atlassian or GitLab and Google hasn’t bought the other one. Maybe owning a developer platform is core to Microsoft’s DNA in a way that it could never be for a retailer or advertising company, but the synergies of having a developer platform to complement your cloud platform are obvious.

> It’s surprising that Amazon hasn’t bought Atlassian or GitLab and Google hasn’t bought the other one GitLab and Google would have much better "synergy" since GL already runs on GCP. The ruby may be a culture clash, but I wouldn't put it past Google to have some tooling to help GL straighten out their ruby mess Secretly, though, I want Google to buy Atlassian just to send it to KilledByGoogle

Oh God, please don’t let gitlab get sold out to some big corp.

Re: GitHub Introduces Copilot Extensions

#8

Post by impulser_ »

ralph84 wrote: post #3
bnchrch wrote: post #2

This type of vertical integration must have Amazon a little worried. For example, if Microsoft took a chapter from Apples (anticompetitive) playbook with Spotify, They could always make Azure Extensions N features ahead of equivalent AWS Extensions. The productivity gains vscode devs would have by using Azure would always be more than AWS, and the cycle of user lock in would march forward.

It’s surprising that Amazon hasn’t bought Atlassian or GitLab and Google hasn’t bought the other one. Maybe owning a developer platform is core to Microsoft’s DNA in a way that it could never be for a retailer or advertising company, but the synergies of having a developer platform to complement your cloud platform are obvious.

Google owns 15% of GitLab and they are the largest shareholder outside of GitLab itself.

Re: GitHub Introduces Copilot Extensions

#9

Post by throwup238 »

rohansood15 wrote: post #7

The sentry demo makes me wonder if this chat-based, IDE interface would be the preferred go-to for Devs for multi-tool, multi-step workflows? Or would they prefer to automate the flow as a background, asynchronous task?

> Or would they prefer to automate the flow as a background, asynchronous task?

Definitely want to use it for automation. When writing bindings for a large library it's helpful to have a script that picks several files as implementation examples then has Copilot write the rest by i.e. looping over library headers.

Post reply on HN