Hacker News Reader

Most people use the term self-hosting (or self-hostable) instead of ejectable.

One of the important points of an ejectable app is that you can easily move back and forth between cloud and self-hosted.

You can always start with the cloud version and then transfer to self-hosted if you change your mind and continue right where you left off. Not just that, you can also move from self-hosted back to cloud. That makes it easier to get start with a service because you're free to change your mind without lock-in or risk of painful migrations.

Most software apps that I've seen that are actually "ejectable" and use the "eject" verbiage are unidirectional. Not bidirectional. Meaning you eject once and any changes you make drift from the original implementation make it incompatible to go back. Example I know off the top of my head would be Draftbit. Visual Basic / .NET WYSIWYG would be another example. Both low code platforms, but that's usually where I see people talking about "eject"

I think that ensuring data can load back into a hosted service is a losing proposition.

As software updates, the shape of data changes. This would make a significantly harder problem to solve.

Reply on news.ycombinator.com