Hacker News Reader

It should only take a couple of days to switch those to a different cloud provider. When building a Jamstack website there is only very thin logic in the Lambda itself, and S3 is only used as managed file storage.

S3 is just files and Lambda is just FaaS, you can host your own open source versions of these tools and not encounter an issue.

This would be a more solid argument if they were using a lot of AWS features together, but you could replace this with Minio and FastCGI if you really wanted to.

and GitHub...

Are they locked into github (using their proprietary APIs) or just using it as a git backend (using standard git tooling)? It's not clear from the article.

I'm pretty confident they're going to handle PRs via the github interface. I don't think they'd get many contributions if you had to email patches in.

right, tho the github lock-in is probably gonna be the least worse if they mostly rely on git itself (GH issues and PRs can be migrated to other providers or self-hosted a lot more easily than uncoupling yourself from AWS APIs and services).

And kubernetes, and react, and mysql. How to add something apple to the mix?