))
BBS 20: Why we stopped using git
Manage episode 519414735 series 3271778
https://brainsandbeards.com, Wojciech Ogrodowczyk, and Patryk Peszko에서 제공하는 콘텐츠입니다. 에피소드, 그래픽, 팟캐스트 설명을 포함한 모든 팟캐스트 콘텐츠는 https://brainsandbeards.com, Wojciech Ogrodowczyk, and Patryk Peszko 또는 해당 팟캐스트 플랫폼 파트너가 직접 업로드하고 제공합니다. 누군가가 귀하의 허락 없이 귀하의 저작물을 사용하고 있다고 생각되는 경우 여기에 설명된 절차를 따르실 수 있습니다 https://ko.player.fm/legal.
Our video about JJ: https://www.youtube.com/watch?v=J2f3Pj58wTg
Key Moments:
Introducing JJ (Jujutsu): The hosts explain what JJ is, where it came from, and how it works as a Git-compatible version control tool.
Why JJ works alongside Git: They highlight that JJ can be used on top of existing Git repositories, allowing silent adoption without requiring team-wide changes.
Undo/redo & operation log: A major selling point — JJ’s intuitive ability to undo any action and track every change, unlike Git’s cryptic reflog.
Working with changes, not commits: JJ’s model fits developers’ real workflow better, allowing editing of earlier changes, easy restructuring, and meaningful commit histories.
Goodbye git stash: JJ removes the need for stashing or temporary commits when switching context, making branch changes effortless.
MegaMerge capability: JJ allows temporary merging of multiple branches for testing without permanent commits — something Git can’t replicate cleanly.
Improved review workflow: JJ makes checking out others’ branches and cleaning up afterward much easier compared to Git’s messy local branch management.
Tools & ecosystem: Terminal UIs, graphical interfaces, and merge tools already support JJ, making it beginner-friendly.
Path to wider adoption: Discussion about the future potential of a “JJ hub” that works natively with change IDs.
Closing reflections: Both hosts emphasize that switching to JJ was easier and more valuable than expected — enough to inspire them to restart the podcast.
👋 Visit us on https://brainsandbeards.com/
23 에피소드
공유
