Conversation

Notices

1. Embed this notice
   iced depresso (icedquinn@blob.cat)'s status on Wednesday, 14-Oct-2026 00:43:43 JST iced depresso
   you're silly posting if you think git actually won the VCS wars. *github* won that fight.
   • Embed this notice
     SuperDicq (superdicq@minidisc.tokyo)'s status on Wednesday, 14-Oct-2026 00:48:46 JST SuperDicq

     in reply to

     @icedquinn@blob.cat It's kinda true. The real workflow intended for git (sending each other patches through email and having the actual repository decentralized) most people don't know about.
     
     All people know is the variant of git popularized by Github with centralized repo with a pull request interface which is what forgejo and others have copied too.

   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Wednesday, 14-Oct-2026 00:50:27 JST iced depresso

     in reply to

     • :marseyloadingneon: m0xEE :marseyloading:
     @m0xEE social features.
     
     there were already forges before github but you had to set them up. stuff like trac was used a lot. github just made it fit the "i can't be bothered to spend effort learning anything" mould.
     
     its sort of nice to have issue tracking and stuff to hand but also kind of feels stagnating like now people expect to be able to shit directly in to the ticket queue (and also the ticket queues are significantly more anemic than when we used Phabricator or Roundup.)
   • Embed this notice
     :marseyloadingneon: m0xEE :marseyloading: (m0xee@breloma.m0xee.net)'s status on Wednesday, 14-Oct-2026 00:50:29 JST :marseyloadingneon: m0xEE :marseyloading:

     in reply to
     @icedquinn
     Why do people even use forges?
     And GitHub is so slow now that making a shallow clone of a medium-sized repo might be faster than trying to find something via web UI.
   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Wednesday, 14-Oct-2026 00:51:42 JST iced depresso

     in reply to

     • SuperDicq
     @SuperDicq well the git command line is complete ass, so.
     
     mercurial and darcs made all the good decisions when it came to UX.
   • Embed this notice
     SuperDicq (superdicq@minidisc.tokyo)'s status on Wednesday, 14-Oct-2026 00:51:43 JST SuperDicq

     in reply to

     @icedquinn@blob.cat A lot of don't even directly use the git command line tool. They interface with it using the proprietary github cli or gui.

   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Wednesday, 14-Oct-2026 00:52:57 JST iced depresso

     in reply to

     • SuperDicq
     • snacks
     @snacks @SuperDicq i know about the existence of forge cli tools because i see things but i've never used it.
     
     i think they mostly get used when you're stuck suffering shit like github's UI when there's 200 open issues and your triage capacity is "marked wontfix."
     snacks likes this.
   • Embed this notice
     snacks (snacks@netzsphaere.xyz)'s status on Wednesday, 14-Oct-2026 00:52:59 JST snacks

     in reply to

     • SuperDicq
     @SuperDicq @icedquinn i only learned about the github cli because claude wants to constantly use it lol
   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Wednesday, 14-Oct-2026 00:55:44 JST iced depresso

     in reply to

     • SuperDicq
     • snacks
     @SuperDicq @snacks my endless laughing forever about MCP is it finally got everyone to re-add the rexx port to software (and also document it in the process) which are two things everyone emphatically asserted simply could not be done because they just never felt like doing it.
   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Wednesday, 14-Oct-2026 00:55:45 JST iced depresso

     in reply to

     • SuperDicq
     • snacks
     @SuperDicq @snacks kind of surprised they didn't add an MCP endpoint as much as github loves LLMs
   • Embed this notice
     SuperDicq (superdicq@minidisc.tokyo)'s status on Wednesday, 14-Oct-2026 00:55:46 JST SuperDicq

     in reply to

     • snacks

     @snacks@netzsphaere.xyz @icedquinn@blob.cat Or people don't even interact with the github cli anymore because fucking slop tools do it for them now.

     snacks likes this.
   • Embed this notice
     SuperDicq (superdicq@minidisc.tokyo)'s status on Wednesday, 14-Oct-2026 00:57:02 JST SuperDicq

     in reply to

     • snacks

     @icedquinn@blob.cat @snacks@netzsphaere.xyz MCP is a meme anyway that makes everything overcomplicated. LLMs are much better at just calling cli tools directly than interacting with a special API made for them because they are trained on human writing and what humans do.

   • Embed this notice
     iced depresso (icedquinn@blob.cat)'s status on Wednesday, 14-Oct-2026 01:22:53 JST iced depresso

     in reply to

     • SuperDicq
     • snacks
     @SuperDicq @snacks its just json-rpc with a handshake. the spec page makes it sound fancier than it is
     snacks likes this.
   • Embed this notice
     mischievoustomato@0.5dollah.click's status on Wednesday, 14-Oct-2026 01:24:59 JST mischievoustomato

     in reply to

     • SuperDicq
     • snacks

     @SuperDicq @icedquinn @snacks i only interact with the gh cli when i have to gh auth login

   • Embed this notice
     SuperDicq (superdicq@minidisc.tokyo)'s status on Wednesday, 14-Oct-2026 01:33:41 JST SuperDicq

     in reply to

     • Phantasm

     @phnt@fluffytail.org @icedquinn@blob.cat I never said the intended workflow was good for big projects. Just saying that's what is intended and that Github popularized a completely different workflow that is now the defacto standard even on other Git hosts that simply copy it.

   • Embed this notice
     Phantasm (phnt@fluffytail.org)'s status on Wednesday, 14-Oct-2026 01:33:42 JST Phantasm

     in reply to

     • SuperDicq
     @SuperDicq @icedquinn
     >The real workflow intended for git (sending each other patches through email and having the actual repository decentralized) most people don't know about.
     
     The intended workflow also sucks ass. It only works if you have a single person managing a whole subsystem of a project where all the patches to it go against a common base for everyone for that subsystem. Once you start mixing different startpoints from a moving branch, it completely falls apart.