Forget about dating. If you want the AI to be able to send texts from your number, and you own an iPhone, I think your only other choice would be to port your number to Google Voice?
I think the parent has a valid point. The actual README says "inspired by Apple’s Private Cloud Compute".
I think it's more fair to say it implements the same idea but it is not an opensource implementation of Apple's Private Compute Cloud the way e.g. minio is an implementation of S3, so the HN title is misleading.
I didn’t pull any stats but I’ve been working at Google for most of the last 10 years (in two stints).
And actually I think even 10K is a very generous upper bound, really if I were betting money I’d peg it at like maybe 2000 engineers that use golang as their primary language and a big chunk of those are SWE-SRE?
There's just _way_ more Java and C++ than there is golang…
Your experience doesn’t invalidate the likeliness part of the parent comment.
You just happen to be in the subset / cluster / areas that write in golang. Probabilistically speaking across the entire Google engineering population both you and the teams around you are outliers. That doesn’t mean golang is insignificant.
As to whether golang was worth it I disagree with the parent, I think it was probably worth the resources invested, even if e.g. usage has leveled off internally, but at any rate this is a hard thing to measure so we’re all just opining.
You might be, but as the parent said, it’s not likely. I think that’s a fair statement, out of 100K engineers or whatever it is, I’d estimate less than 10K of them are writing primarily golang code.