Skip to content
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

Closed
kevinjpetersen opened this issue Jan 29, 2016 · 8 comments
Closed

Support for the SDK's future #7

kevinjpetersen opened this issue Jan 29, 2016 · 8 comments

Comments

@kevinjpetersen
Copy link

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?

@yamill
Copy link

yamill commented Jan 29, 2016

+1

@batiron
Copy link

batiron commented Jan 29, 2016

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.?

@carlbrusell
Copy link

+1

@gfosco
Copy link
Contributor

gfosco commented Jan 29, 2016

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 gfosco closed this as completed Jan 29, 2016
@andhieka
Copy link

@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.

@gfosco
Copy link
Contributor

gfosco commented Jan 30, 2016

No, it definitely wasn't about that. I think it makes sense in a way, financially, and have come to accept it.

@lacker
Copy link
Contributor

lacker commented Jan 30, 2016

FWIW, if you are curious about "why", I think this NYT article has the best explanation out there.

http://bits.blogs.nytimes.com/2016/01/28/facebook-to-shut-down-parse-its-platform-for-mobile-developers/

@andhieka
Copy link

@gfosco @lacker Thanks for enlightening me! 👍

kylekasky pushed a commit to kylekasky/parse-server that referenced this issue Jan 12, 2023
…o-ope (pull request parse-community#7)

LIS-869 removed params from file name
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants