arxanas

16 ms·

121.
by arxanas 5y ago
https://github.com/martinvonz/jj is a promising alternative which fixes many of the design mistakes of Git, but can still interact directly with Git repositories.
122.
Git-stack: Stacked branch management for Git(github.com)
23 points by arxanas 5y ago|3 comments
123.
by arxanas 5y ago
Chording keyboards have become significantly more popular among software engineers, although they're still not popular in an absolute sense. Check out https://www.openstenoproject.org/ and its Discord server for a vi
124.
Jujutsu DVCS(github.com)
1 points by arxanas 5y ago|0 comments
125.
by arxanas 5y ago
I didn't see a way to post a comment on the article, so I'll post here. Regarding performance concerns, my own project https://github.com/arxanas/git-branchless is designed to work very fast at monorepo sca
126.
by arxanas 5y ago
I found this post to be very high quality: https://news.ycombinator.com/item?id=26710763
127.
by arxanas 5y ago
Update on this: since October 4, I've received an additional 17 emails, of which 5 generated useful discussion, and 2 out of those 5 had legitimately interesting opportunities. Also, despite having set up SPF and DKIM, LinkedIn continu
128.
by arxanas 5y ago
Can you expand on why this is unkindness? I've generated lots of very useful discussions with recruiters, with four serious leads for companies I'm interested in, and also rejected many companies immediately based on compensation.
129.
by arxanas 5y ago
Recruiter emails are so generic that you can do this automatically! https://blog.waleedkhan.name/detect-recruiter-spam/ It's actually saved me a lot of time and led to several high-quality conversations with recru
130.
by arxanas 5y ago
git-branchless doesn't (yet) aim to integrate with hosted Git providers in any particular way. You just use remotes and push as normal. I think the CLI is mostly at parity in terms of features. git-branchless has `git undo` while gt ha
131.
by arxanas 5y ago
There are decentralized monorepos, such as gecko-dev ( https://github.com/mozilla/gecko-dev ), which presumably has several forks in products like Iceweasel. I think the monorepo workflows which Git isn't good at ar
132.
by arxanas 5y ago
Why would this indicate that monorepos are the problem?
133.
by arxanas 5y ago
It makes more sense if you think of the index as a structure meant specifically to speed up `git status` operations. (It was originally called the "dircache"! See https://github.com/git/git/commit/5a
134.
by arxanas 5y ago
Thanks for the feedback. I also received this request today to document a relevant workflow: https://github.com/arxanas/git-branchless/issues/210 . If you want to be notified when I write the documentation (ho
135.
by arxanas 5y ago
The index as a data structure is really starting to show its age, especially as developers adapt Git to monorepo scale. It's really fast for repositories up to a certain size, but big tech organizations grow exponentially, and start to
136.
by arxanas 5y ago
You might be interested in my project https://github.com/arxanas/git-branchless , which is intended to replicate such a workflow.
137.
by arxanas 5y ago
You might find my blog post on some of the uses interesting: https://blog.waleedkhan.name/union-vs-sum-types/ In a language like TypeScript, they can be used for function overloading since there is no runtime dispatch
138.
by arxanas 5y ago
Explanation: A record is a set of key-value pairs with the value having a given type (also called a struct, object, etc. depending on the context). In TypeScript, this is an example of a record: const foo = { bar: 1, baz: "qux&
139.
by arxanas 5y ago
The piano teachers I've worked with don't seem to know enough about kinesiology to explain the muscle activity. On the contrary, it seems like the mental models they use to explain posture and exercises are primarily correlative,
140.
by arxanas 5y ago
This was interesting to me. I played chess seriously for about 4 years and gained about 400 Elo points. Apparently that's rather above the expectations for an "ordinary" person! I spent around 1000 hours practicing chess duri
141.
by arxanas 5y ago
This book has a lot of useful techniques regarding piano practice , but it's light on details about technique itself, such as finger positioning or how to engage which muscles. Does anyone have good resources towards this end?
142.
by arxanas 5y ago
The book uses a lot of hyperbolic wording, but the techniques in the book are generally sound. Mental practice in particular is an established pattern for top performers across sportive disciplines.
143.
by arxanas 5y ago
Under git-branchless, this workflow is: $ git checkout <commit> $ git commit --amend $ git restack It will properly rebase descendant commits and branches for you.
144.
by arxanas 5y ago
I disagree here. The tooling is a big problem. If you revise one of the earlier commits, it's pretty hard to coax Git into rebasing the dependent commits and branches properly.
145.
by arxanas 5y ago
Yep, that's precisely the scenario which git-move is intended to improve on. I also recommend that you try out a solution like git-stack to manage stacked PRs: https://github.com/epage/git-stack
146.
by arxanas 5y ago
Why is that? There's some evidence that the name is intuitive: https://github.com/arxanas/git-branchless/discussions/45#dis...
147.
by arxanas 5y ago
No. See also my comment here https://news.ycombinator.com/item?id=28900781 . The work isn't directly compatible, and the equivalent upstream work is already underway.
148.
by arxanas 5y ago
Author here, happy to answer any questions. I also recommend you check out the rest of the `git-branchless` suite, which contains other helpful tools, such as commit graph visualization and a commit graph undo feature: https://gi
149.
by arxanas 5y ago
I found it very hard to motivate a lot of the other features. Many people don't use and don't see the value of tree-based development. See this feedback from a user: https://github.com/arxanas/git-branchless&#
150.
by arxanas 5y ago
You can see in the demo performance on `gecko-dev`, which is a Git mirror of a Mozilla repo. You probably need to have 500k+ commits/100k+ files before it starts being useful. My work has a large Git monorepo, which is why I made this

More ›