Future of this project

[xavdid]

Now that parse.com is officially shut down, it's worth having a discussion about the future of this project.

Since I imagine most of the current parse users will either be using javascript (or a hosted solution, but that's $$ and the original draw of parse was the lack of cost), the active maintenance of this gem makes less sense than it did a few years ago.

For me personally, the shutdown means I don't really use Parse for anything anymore. Separately, I write less ruby code than I used to. Between those two factors, my devotion and ability to maintain this (awesome) library hasn't been what it could be. @rhymes is doing an awesome job and if they've got the time/need for it, there's no reason to shut anything down.

So really, the purpose of this is to get a feel for how much demand there is here and as a result, what sorts of resources we should try to allocate.

Thanks for reading!

[rhymes]

Hi,

after the shutdown (actually before that) many hosted Parse Servers popped up (see https://www.sashido.io/, https://www.nodechef.com/parse-server, https://www.back4app.com/ and more).

It is true that many people just migrated away from Parse altogether but some just took the easier route of self-hosting o using one of the mentioned hosted services. In the case of a client I work for I had to setup two Parse Server installations on Heroku and we still use parse-ruby-client to communicate with those servers, though it's just a temporary solution until they migrate the mobile clients away from Parse altogether.

I myself have not much time to keep maintaining this library and I agree there's probably less interest in it (not much to begin with?) but I would try to reach the mythical 1.0 anyway.

[olleolleolle]

👋 Using a Parse community server here.