Hacker News Reader

Curious about this. The usual argument is that hosting on Cloudflare is vendor lock-in, I am stating that picking _any_ SaaS induces vendor lock-in.

> No matter what choice you make, it's always going to be vendor-locked in. Switching out something, even if it's open source and self-hosted, means that you're rewriting a lot of code.

The argument is that you might as well not "spend" those 5 taxes, just use the platform, and write the software.

View on HN

The title strongly implies that vendor lock-in is a bad thing (the phrase "lock-in" has a very much negative connotation), but then the article proposes that you should just give up and go all in on vendor lock-in with a proprietary platform. The alternative to vendor lock-in with SaaS would naturally be running standardized open-source or home grown solutions. That is what people who complain about vendor lock-in generally recommend, not SaaS. The article would be more clear if it addressed that.

Ok, that's fair. I think I might have approached this from a typical JavaScript/ TypeScript developer - where using SaaS is the norm. I'm wondering what you developing in? Not wishing to invalidate your point, just curious?

We're a Rails shop generally using basic Postgres + Redis with various Rails gems filling in where needed. Our needs aren't terribly complex though.

Reply on news.ycombinator.com