r/iOSProgramming • • Jan 28 '16

Announcement Parse.com is shutting down

http://blog.parse.com/announcements/moving-on/
161 Upvotes

206 comments sorted by

View all comments

Show parent comments

-1

u/quellish Jan 29 '16

I doubt there will be much outcry about the move being unethical, but I believe it is.

Parse was providing a service as a product, that product was their business. They announced they are discontinuing the product and are providing time and resources for their customers to transition. How is this not morally correct?

Who knows if Parse ever became profitable. I was referring to their quarterly earnings.

Are the quarterly earnings from Parse available?

A year is generous however it doesn't change the fact that a lot of developers wrote code that will inevitably become outdated and unsecure.

Facebook screwed ya over.

What were you expecting to happen?

1

u/ThePantsThief NSModerator Jan 29 '16

Who knows if Parse ever became profitable. I was referring to their quarterly earnings.

Are the quarterly earnings from Parse available?

I'm not sure he was talking about Parse at all; my argument would be that Facebook has the money and the manpower to keep it rolling period. They're all about cool things, this decision doesn't make sense to me...

0

u/quellish Jan 29 '16

I'm not sure he was talking about Parse at all; my argument would be that Facebook has the money and the manpower to keep it rolling period.

Why would they "keep it rolling" if it was losing money or didn't make business sense?

1

u/ThePantsThief NSModerator Jan 29 '16

There are a number of things they could do to keep it rolling without costing them anymore money. Instead of shutting it down a year from now could start charging everyone a year from now as well as open source the server code like they already have, or they could sell it, etc.

1

u/quellish Jan 29 '16

There are a number of things they could do to keep it rolling without costing them anymore money.

Like? Doing anything costs money. Parse has probably been a money losing effort for some time. It uses more resources than it brings in. For it to use no resources but produce a product or service would be.... impressive.

Instead of shutting it down a year from now could start charging everyone a year from now

They could, but that may make no business sense for a lot of reasons. They may have reason to believe that if they charged everyone that there would not be enough paying users after a few months to keep things running. Or this may just not be a business that Facebook feels fits with where they want to go. Or they may feel there will be no market for Parse in the future. All of these things are plausible.

-1

u/dcpc10 Jan 29 '16 edited Jan 29 '16

How is this not morally correct?

Depends on what you define as morally correct.

I would have preferred that they downsized, simply maintained the codebase. This is totally something that could have been done, Facebook has many subsidiaries and I doubt all of them generate profit. Would certainly make for an easier transition. (Instead of shutting down their services, I would prefer increased pricing, less support, less feature development, etc.)

2

u/quellish Jan 29 '16

I would have preferred that they downsized, simply maintained the codebase.

They are doing that. That is in the annoucement. Parse will remain up for a year. They are open sourcing the server and providing transition tools. That is downsizing and maintaining.

2

u/dcpc10 Jan 29 '16

No it is not, that is called shutting down the business. What purpose does a service have if it is one year from shutting down? Quite frankly you are misunderstanding what I am saying.

1

u/ThePantsThief NSModerator Jan 29 '16

That is downsizing and maintaining.

Now you're just being pedantic. You know what he means. We want them to maintain it indefinitely, not simply for the next year until it vanishes.

-1

u/quellish Jan 29 '16

Now you're just being pedantic.

No, it's not. They're doing what he's describing.

We want them to maintain it indefinitely, not simply for the next year until it vanishes.

Yeah, and I'd like my Newton to be covered by AppleCare, but that ain't going to happen. Parse would go away eventually. Google will go away eventually, so will Apple, so will the iPhone.

1

u/ThePantsThief NSModerator Jan 29 '16

They're doing what he's describing.

You're still being pedantic, because you knew that isn't what he meant. He could have meant one of two things and it's pretty obvious what he meant.

Parse would go away eventually. Google will go away eventually, so will Apple, so will the iPhone.

Now you're being really pedantic. We're all going away at some point. Nothing really matters. Why bother?

0

u/quellish Jan 29 '16

That reminds me of a story.

Several years ago a new developer joined my team. We had a library of well, mostly category methods (ug) that wasn't well tested. The application depended on it, but parts of it would get "fixed" every few releases. So for this developer's first project we had him write tests for the library. A lot of it was various NSString-things and the expected behaviors were well defined. We wrote that up in a lot of detail - this method should handle strings of this length and do this with them, it should handle nil strings as input, it should return this error under these conditions.

So a couple of weeks(!) later this guys says he's done, closes out the ticket and moves on to other work. Hours after that the tests are failing and he's frantically working to figure out why. Someone else on the team IM's me something from one of the tests:

- (void) testAwesomeStringWithStringCanHandleNil {
	NSString *string;
	NSError *error;

	string = [NSString awesomeStringWithString:@"nil" error:&error];

Soooooo I ask him about this test. He doesn't see the issue. I point out that @"nil" isn't... nil. It's not testing what it's supposed to test.

Him: "Well, that's a matter of opinion".

I guess I was just being really pedantic. I expected an Objective-C developer to understand that nil was not the same as @"nil".

You're still being pedantic, because you knew that isn't what he meant.

No, I did not, and I had no reason to infer it. He said he wished they had downsized and kept it running. They are doing exactly that.