Capaj

8 ms·

1. 1.▲
   by Capaj 2mo ago

   yes that is exactly the main usecase for this
2. 2.▲
   by Capaj 2mo ago

   I use it as my daily driver for any git operations, but most people prefer command line. So for a typical person it is useful early in their developer career as a helper when learning git.
3. 3.▲
   Ingit – Git GUI that runs in the browsers(github.com)

   8 points by Capaj 2mo ago|5 comments
4. 4.▲
   by Capaj 2mo ago

   I was a disgruntled user of ungit for the past 10 years. Even considered rewriting it myself manually like 5 years ago. Well not anymore. In the past few weeks I built a fast, animated git GUI from scratch ingit makes branch switching, merg
5. 5.▲
   by Capaj 5y ago

   No it's not. Even if they fixed all the bugs which I doubt the API design is bad.
6. 6.▲
   by Capaj 6y ago

   > It's great for the frontend, but in this case it's awful for the backend. So what you are saying is it's better to leave this complexity for the frontend developer to handle on the client side? Very wise!
7. 7.▲
   by Capaj 7y ago

   > If an ID is required for all queries the docs should say so. they absolutely should. It's not really needed every time, but when you have a queries with IDs and without-that's when the cache blows up. They even a have a snaps
8. 8.▲
   by Capaj 7y ago

   > Also IDs aren’t required for cache updates, only the typename. this is very inacurate. The problem happens when an items is cached with an ID and then another GraphQL request tries to cache it without and ID or vice versa. This is wher