Teams have been building services like this for ~20 years. They very rarely stick. I agree that it’s still too hard, but the market has historically been too small. It’s at-best a hobby side project for a larger company that can afford to burn the cash.

Like Apple offers this for email for iCloud users. I think Firefox Relay offered it too. There was another company in the late 00s that offered a P2P version.

I mean _cool_, but I’ve not seen a company with this as its primary product last more than 18 months before. With that, _good luck_.

Unless I personally gave you my work email address, you can f*k right the hell off.

Buying a list of email addresses off the internet that has mine in it is top-tier shady.

1. If you have $800 to spend on an emotional support robot — OR you’re dumb enough to spend $800 on an emotional support robot, I don’t see this as a big loss.

2. Never spend money on multiplayer-only video games. Never buy a robot that is 100% cloud connected — ESPECIALLY from a startup. This is the same concept stated twice.

3. You buy things for what they are today; NEVER for what they might be tomorrow.

I feel no remorse. Stupidity should be painful.

People hate Windows, but won’t stop using it.

Everyone gets to make their own decisions, I suppose, but let’s all tell the truth about what’s happening here.

Ones that are highly complex but poorly documented.

I used to own an API service at work, where we worked hard to ensure that the documentation was of a very high quality. When I got promoted and moved to a new team, I'd warned my manager NOT to hand it over to one team that was remarkably bad at their work. My manager did anyway.

During the transition, the new development lead said "I'm not going to read the documentation. If the code isn't self-documenting, we're going to rewrite it." Note that he said that not knowing anything about the service they were taking over. Also, it was in a language that had never established strong patterns for itself, so self-documenting when there are no strong patterns is generally meaningless.

Over the next 6 months, he proceeded to ruin the service to the point where it was impacting customers, and got fired for it. In any project of large enough size, self-documenting code falls apart unless you are remarkably good at it. IMO, Go's standard library is an exception to my experience.

I disagree with most of these posters. I am a person on GitHub. I don’t become a different person once the work day starts. I’ve done plenty of OSS as an employee of companies, and I’ve done more OSS work as an individual.

Although you _can_ use separate accounts, the idea that you MUST is nonsense.

But yes, I encountered the same thing once I was added to my full-time employer’s GHE Cloud account. So far, not a problem.

I play instruments, read books, and have an iPad.

It reminded me of the old magazine clipping of a guy holding a camcorder over his shoulder and pointing to a table full of technology. "All of this fits in your pocket now."

Same thing. Chill out. You're free to not like something and have it continue to exist despite your dislike of it.

FFS

> In fact I think it’s symbolic of the direction Apple took since the passing of Steve Jobs.

…aaaaaand I've tuned-out.

So much this.