Hacker News new | past | comments | ask | show | jobs | submit login

I have no idea. But I do know that I'm not giving control to some walled garden that can yank it at a moments notice.

Might as well be a Facebook page.

Why is the youth so adverse to owning their own data?

It's just static pages. All the code is in your Gitlab/GitHub repo. I wouldn't call Netlify a walled garden, but the workflow definitely does not imply a situation where you'd lose your data in the unlikely event that Netlify goes down or closes shop.

I don't see any vendor lock in evident in any of this. Plenty of flexibility to both move your git code to your own self hosted git, and quite easy to host it on your own webserver on DO or wherever instead of Netlify.

What are you referring to as "walled garden" here? (Also, what does this have to do with "youth"?)

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact