I sadly didn’t share that experience - I fed it my goodreads most recent - but it largely picked up on 2 or 3 series I’ve been slowly working my way through so that most of the recommendation list was ALL the other books in the series (and the spin-off series) so I didn’t really get anything useful…
One of the NetBSD developers is a Mercurial developer and I think the general plan for a while has been to switch to Mercurial once a few technical issues have been fixed. I'm not sure if that has fully happened now and it is just waiting on the right people having enough time or what the status is. I think NetBSD and OpenBSD are the last two actively maintained open source projects that use CVS, at least as far as I am aware.
However, at least for NetBSD (don't know about OpenBSD) there is an official mirror on Github and you can submit pull requests there if you want (I'm fairly sure this will stay the case even after a switch to Mercurial). Some of the main developers mostly use git until a commit is almost ready. I think the main practical difference from the project using git as the main repository for anyone who doesn't have commit access is that while commit messages will mention the contributor I don't think it is linked on github to the contributor in the same way it would usually be with an accepted pull request. At most there might be a tiny number of extremely minor issues with the repository conversion left, and I think those might have been fixed by now as well.
If it works for them why not, and compared to rcs it's really not too bad ;)
In some aspects the old centralized versioning systems are superior to distributed systems like git (for starters, they give you a single linear history with incremental revision numbers).
Why are the words 'Computer Vision' not above the fold on the front page? How am I supposed to know that CV stands for Computer Vision rather than Curriculum Vitae?
I've seen a bunch of companies do this. The problem is always that it isn't Excel. This means usually things like XLWings, Excel-DNA, etc. are actually more useful.
I have the same issue as author, and what you said was also my initial guess, but after a careful inspection i can assure you that there is nothing in the port (scrapped with end of zip tie to not damage anything inside) and cable is in fact applied fully in the port. I also tried different cables that fit correctly before and still fit in other devices, so in my feel there is very little chance that this is anything other that port fault. It's pixel 2xl if that's important for anyone.
There has been several articles about this man recently. I come away from them wanting to help him financially. I feel if you're going to publish an article about him, and make money from adverts on your website, you have a responsibility to try and help this man. If not it's just exploitation.
The only thing that might make Apple improve their documentation is if there was evidence that people started actually abandoning Apple's platforms.
Currently it seems there is a never ending supply of developers ready to gamble years of their careers on Apples Terms & Conditions, and while these same people usually eventually realize that there's ultimately no money to be made, they are replaced with a new generation seeking an AppStore paved with gold. Until that stops, the docs will stay piss-poor.
While I have often used a Mac for development and enjoyed it, I don't often actually develop anything for macOS or iOS because, well, why would I risk my livelihood on Apple's whim? They regularly destroy developer's lives with no thought or consequence.
There is a lot of money to be made working on iOS for big corp. hell, even small startups.
You seem to allude to indie devs though, so I can agree that it would be insane to attempt to go out on your own without essentially being a startup in your own right.
