I'm still using Mercurial whenever I can (including work!). The Tortoisehg GUI is good for doing reviews, and the command line is comfortable.
I grew up on CVS and then Subversion. Played with Bazaar a little, mainly because it could use an SFTP location as the back-end.
And I still avoid Git if I can help it. I would/do figure it out when I have to, but it never feels comfortable. Such is my avoidance that I'm dabbling with Jujutsu although I'll still need to really sit down and read through it some more to grok the way it works.
When I tried Fossil it had things weirdly separated.
I was expecting when I make a commit, I would have the facility to specify what issues it addressed and it would close them for me automatically. It seemed there is so much opportunity there to "close the loop" when the issue tracker, etc and integrated in your VCS, but it wasn't taken.
This is a current architectural limitation, manifests (defining check-ins) and tickets are different types of artifacts and you cannot combine the card types into the same artifact. Changing this would likely break backwards compatibility with previous Fossil versions and I'd expect resistance. It may still be worth bringing up on the Fossil forum if you desire the feature.
Personally speaking though, I don't want things automagically closed GitHub-style based on parsing a check-in comment. An issue ought to be closed with intention.
> I don't want things automagically closed GitHub-style based on parsing a check-in comment.
Sure, I get that. I was just disappointed that none of the project management stuff seemed terribly integrated in any way from my brief review. It seemed like opportunities there that were not taken.
My mum's dementia has recently worsened to the point that she cannot figure out how to use the phone to ring people. She just finds it confusing and has caused her a great deal of distress.
I ended up installing Big Launcher[1] as an alternative android launcher and configured it so it has buttons to ring three people. That's it. Even then, then confirmation yes/no dialogue when she presses "End Call" gave her a lot of anxiety initially.
I recently had to setup access to a local streaming service on my step-dad's TV recently. The amount of hoops necessary, including installing their stupid app on a phone, and entering passwords for several different accounts, several times, was absolutely ridiculous. Being technologically adept I found it an absolute PITA. It was a complete non-starter for him.
My point is that your, "If he can afford a season pass, he can afford a smartphone," comment comes across almost as callow as the attitude of the Dodger Stadium management towards the very real issues of getting old in a world that is moving faster and faster technologically.
In the case of Google Workspace for our company, I'm using Cubebackup[1]. I've been going through the disaster recovery exercises lately, and thinking about what I've been calling "external backups", which are backups of a service that are stored and restorable outside that service.
It can be surprisingly difficult with a lot of SaaS products (including Google).
The Australian sulfur-crested cockatoos are pretty smart. They would teach each other how to open heavy bin lids to raid the garbage. I seem to remember they would even team up to do it. There are studies about how this behaviour spread from suburb to suburb in Sydney.[1]
More recently they've figured out how to operate drinking fountains.[2][3]
I grew up on CVS and then Subversion. Played with Bazaar a little, mainly because it could use an SFTP location as the back-end.
And I still avoid Git if I can help it. I would/do figure it out when I have to, but it never feels comfortable. Such is my avoidance that I'm dabbling with Jujutsu although I'll still need to really sit down and read through it some more to grok the way it works.
reply