3 ms·

Devs say a lot of uninformed things. With a heavy predisposition to hating the "legacy" monoliths that are Microsoft and by association GitHub. Yes, Copilot su

Devs say a lot of uninformed things. With a heavy predisposition to hating the "legacy" monoliths that are Microsoft and by association GitHub. Yes, Copilot supports skills. Practically all agents support very similar feature sets or are actively building up parity support if not already there. The only real difference between systems is the prompt and payment method. Copilot even allows you to use Anthropic's own skills repository: https://github.com/anthropics/skills https://github.com/anthropics/skills https://docs.github.com/en/copilot/concepts/agents/about-agent-skills https://docs.github.com/en/copilot/concepts/agents/about-age... details the support for skills. https://docs.github.com/en/copilot/concepts/agents/copilot-cli/comparing-cli-features https://docs.github.com/en/copilot/concepts/agents/copilot-c... details the CLI tool in general, which seems more or less on par with Claude Code's.

deleted 7mo ago
[deleted]
walthamstow 7mo ago
It's a bit rich to go around calling people uninformed because they prefer one harness to another, particularly when you are recommending GHC as comparable to CC.
- nfg 7mo ago
  Have you used the gh copilot cli? What would stand out most to you as gaps right now?
  - walthamstow 7mo ago
    IME is is less capable of performing complex work, more frequently goes down blind alleys and needs correcting, that kind of thing. It's night and day vs CC.
    - nfg 7mo ago
      And this has been comparing like for like with CC - say Opus 4.6 on the same reasoning effort? Hasn’t been my experience particularly but fair enough. I do tend to use them in different situations (CC outside of work).
      - walthamstow 7mo ago
        Even if it is close, maybe GHC CLI has improved in the last month since I last used it, I know you didn't say it but calling people uninformed because they prefer one or the other is just wrong.
        nfg 7mo ago
        I’d agree, though maybe there’s a more charitable reading of the OP - “uninformed” is one of those accusations that it’s rarely very polite or fair to level against an individual but sometimes is reasonable against a group based on observation. My experience would be that it’s true that “devs says lots of uninformed things” - and I’d include myself in that. It’s been my experience that it’s particularly tough in this space at this time because: 1. Tooling is changing very fast but people tend to form sticky opinions (reasonably enough - there’s only so much time in the world). 2. It’s just hard to form robust objective opinions - you have to make a real effort to build test cases and evaluation processes and generally the barrier to entry there is pretty high. So - I agree, calling people uninformed is not a great way to win them over, but maybe that’s the price of living in a world of anecdotes which become fixed in people’s minds.
    - ValentineC 7mo ago
      That's probably because the 200k context window means that it'll end up compacting things sooner. I've just had a chat with Copilot's Opus 4.6 go off the rails after compaction today.
      - chatmasta 7mo ago
        Make it write a skill and rule hook for PreCompact to do a handoff that explains what was worked on, what to know, and what to do next. If it goes off the rails after compaction then it won’t be great in a new session either, and you want to make sure you maximize continuity or development will be unsustainable. A backlog.md and improvements.md workflow also helps with this (ticket numbers, descriptions, “focus on BACK-0075,” etc.)
- mynameisvlad 7mo ago
  It’s a bit rich to take the most negative interpretation of my statement, and moreso telling of your insecurities that you chose to be so offended. And, ultimately, proving my point. Did you actually explain why you thought it’s superior? Or is it just because GitHub bad? Have you even tried it recently?
abcdefg12 7mo ago
Uninformed devs is what makes this gravy train going. If everybody jumps on gh copilot it will end quick. Unfortunately it’s self defeating to educate them.

deleted 7mo ago

[deleted]

walthamstow 7mo ago

It's a bit rich to go around calling people uninformed because they prefer one harness to another, particularly when you are recommending GHC as comparable to CC.

nfg 7mo ago
Have you used the gh copilot cli? What would stand out most to you as gaps right now?
- walthamstow 7mo ago
  IME is is less capable of performing complex work, more frequently goes down blind alleys and needs correcting, that kind of thing. It's night and day vs CC.
  - nfg 7mo ago
    And this has been comparing like for like with CC - say Opus 4.6 on the same reasoning effort? Hasn’t been my experience particularly but fair enough. I do tend to use them in different situations (CC outside of work).
    - walthamstow 7mo ago
      Even if it is close, maybe GHC CLI has improved in the last month since I last used it, I know you didn't say it but calling people uninformed because they prefer one or the other is just wrong.
      - nfg 7mo ago
        I’d agree, though maybe there’s a more charitable reading of the OP - “uninformed” is one of those accusations that it’s rarely very polite or fair to level against an individual but sometimes is reasonable against a group based on observation. My experience would be that it’s true that “devs says lots of uninformed things” - and I’d include myself in that. It’s been my experience that it’s particularly tough in this space at this time because: 1. Tooling is changing very fast but people tend to form sticky opinions (reasonably enough - there’s only so much time in the world). 2. It’s just hard to form robust objective opinions - you have to make a real effort to build test cases and evaluation processes and generally the barrier to entry there is pretty high. So - I agree, calling people uninformed is not a great way to win them over, but maybe that’s the price of living in a world of anecdotes which become fixed in people’s minds.
  - ValentineC 7mo ago
    That's probably because the 200k context window means that it'll end up compacting things sooner. I've just had a chat with Copilot's Opus 4.6 go off the rails after compaction today.
    - chatmasta 7mo ago
      Make it write a skill and rule hook for PreCompact to do a handoff that explains what was worked on, what to know, and what to do next. If it goes off the rails after compaction then it won’t be great in a new session either, and you want to make sure you maximize continuity or development will be unsustainable. A backlog.md and improvements.md workflow also helps with this (ticket numbers, descriptions, “focus on BACK-0075,” etc.)
mynameisvlad 7mo ago
It’s a bit rich to take the most negative interpretation of my statement, and moreso telling of your insecurities that you chose to be so offended. And, ultimately, proving my point. Did you actually explain why you thought it’s superior? Or is it just because GitHub bad? Have you even tried it recently?

abcdefg12 7mo ago

Uninformed devs is what makes this gravy train going. If everybody jumps on gh copilot it will end quick. Unfortunately it’s self defeating to educate them.