You can do "see only current branch" with the little filter icon when you hover next to a branch. Although I do find myself getting lost amongst branches more easily compared to Sourcetree, I think there's some difference in how filters are combined that isn't ideal (but I can't remember specifics)
You can also go to View in the menu and click "Filter by active branch" (Ctrl+Shift+A).
Also if you, like me, wanted to blame or view history for specific files there does not seem to be a way by clicking in the GUI to achieve it. But by using Ctrl+P you get the command search and can search for "Blame" or "File history".
Another vote for Fork here. Used to use many different UI clients, including ST and Tower but left Tower for Fork. I still add P4 Merge as my external merge tool though. It seems to have the best algorithm and often solves conflicts automatically.
Lots and lots and lots of people make no. 1 work. The issue isn't whether it is a monolith or not. The issue is whether it has good or poor internal architecture.
No 1 can scale to 1000 requests per second. One machine, one db, one application. It is totally doable because so many people do it.
It's just not sexy and doesn't pad you resume. It's boring stuff that just works.
I wish our app only got 1krps. Maybe these conversations should be bucketed by the traffic volume people are handling - it really leads to completely different designs.
Depending on the feed producer. The farmed fish feed that is considered the very best quality has about 50% fished fish in it (and hence has the natural omega3 in it). The other 50% is mostly soy and wheet, but also misc other stuff like flavor enhancers. Low quality feed is mostly land based.
Yeah... I adore Sqlite and upvote anything about it, but I couldn't upvote this article because it was just so poorly informed. It gets the very basics on sqlite concurrency wrong.
reply