-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for the SDK's future #7
Comments
+1 |
I am guessing they will be leaving it as it is on this account and people who are interested to maintain it will start contributing. If this is not the case then i don't know how.? |
+1 |
The SDKs aren't going anywhere, ever, and will continue to be updated.. not only for bug fixes and security, but there are still some features in the works. Eventually, I believe we & the community will evolve the Parse server and client SDKs beyond what was previously capable with just Parse. |
@gfosco Does the termination of Parse service has anything to do with difficulty of scaling Parse to support more users? I'm still trying to wrap my brain around this sudden announcement. |
No, it definitely wasn't about that. I think it makes sense in a way, financially, and have come to accept it. |
FWIW, if you are curious about "why", I think this NYT article has the best explanation out there. |
…o-ope (pull request parse-community#7) LIS-869 removed params from file name
Now with the soon to come (1 year) retirement of Parse, what will this mean for SDK's in general? Will you continue to have these available and up-to-date? Will the SDK's and Parse-Server be further developed overtime, or does "Retirement" mean what it means, retirement / complete stop of further development?
The text was updated successfully, but these errors were encountered: