Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Parse launches JavaScript SDK: Parse for Websites

blog.parse.com

Post reply on HN
Print view View original

31–40 of 112 posts

Re: Parse launches JavaScript SDK: Parse for Websites

#31

Post by alttab »

guelo wrote: post #20

The pricing seems reasonable, free and then goes up to $200/month once you've gained decent traction. Though it's more than double the cost of a VPS that could support 1 million requests and a 1GB database, and that could make all the difference for an ad-supported app with razor thin margins. https://www.parse.com/plans

It could also make all the difference in margins because it might prevent you from hiring backend developers at all. that said, I see multiple problems that need to be overcome.

1) security. what is preventing an end user from opening a js console and going crazy on the db? How can you ensure consistency when the user has access to the code?

2) Growth. if you choose parse as a platform, the lock in seems like it could cause significant pain down the road.

seems great for toys and demos. I would not run a functioning business on it.

Re: Parse launches JavaScript SDK: Parse for Websites

#32

Post by lacker »

lux wrote: post #29

Was just thinking this was the next logical move for Parse to really blow up. Nicely done too! I don't see examples of file handling through the JavaScript API though, did I just miss it?

Right now, we don't have binary data support (which includes file handling) in Javascript. It's a bit different than Objective-C and Java because Javascript doesn't have great native support for a binary data type. So we can't just expose the same API for binary data that we use for native SDKs. We're working on figuring out a really clean way to support binary data, though.

Re: Parse launches JavaScript SDK: Parse for Websites

#33

Post by tocomment »

nbclark wrote: post #30

My take on Parse is that they do the grunt work that is necessary with every new project. I am currently building an iPad game on top of parse, and while the pricing is a bit concerning, I figure one of two things will happen: 1) The game takes off and the $200/mo is affordable 2) The game doesn't take off and the 5mil requests is adequate. The lock-in concerns are valid, but right now their API isn't so mature that…

How does parse save you time building your ipad game?

Sorry if that's a dumb question. I'm still trying to wrap my head around what it is.

Re: Parse launches JavaScript SDK: Parse for Websites

#34

Post by lopatin »

nanijoe wrote: post #26
arturadib wrote: post #22

Hats off. Parse is the first of all these backend-as-a-service startups to face and solve the biggest problem in the web context: user authentication and data security. By offering a full signup service with email verification and user-level control over the database they have eliminated perhaps the most redundant piece of work that just about every web app has had to implement. Lock-in is of course a concern, but th…

I really wish they charged by something other than API requests..as it stands now, I would not even know a reasonable way to pass on the cost to my users.

Whats wrong with estimating the number of API requests the average user makes and figuring out a price based on that?

Re: Parse launches JavaScript SDK: Parse for Websites

#35

Post by tocomment »

pbreit wrote: post #19

I'm still a little confused by what Parse does and when I would use it. It sounds neat for little, proof-of-concept demos but would I consider it for production of something significant? Does this SDK work without the Parse server?

As am I. I'm hoping someone will chime in and get us low tech folks updated.

Re: Parse launches JavaScript SDK: Parse for Websites

#37

Post by equark »

peripitea wrote: post #27
lacker wrote: post #8

Earlier quoted context omitted.

There are two main types of security. Object-level, and app-level. Each object gets access controls that are similar to ACLs in Unix systems. That provides for the sort of security that separates different users' data from each other. On an app-level, you can also control per-class which operations are usable. For more detail, see: https://parse.com/docs/data#security You should be able use these in combination to se…

I still don't get how I, as a malicious (or curious) user with some form of write permission, would be prevented from doing the equivalent of opening up Firebug console and typing while(true){var p = new Post(); p.save();}

What prevents you from doing this with ajax post on every existing website?

Re: Parse launches JavaScript SDK: Parse for Websites

#38

Post by fooandbarify »

peripitea wrote: post #27
lacker wrote: post #8

Earlier quoted context omitted.

There are two main types of security. Object-level, and app-level. Each object gets access controls that are similar to ACLs in Unix systems. That provides for the sort of security that separates different users' data from each other. On an app-level, you can also control per-class which operations are usable. For more detail, see: https://parse.com/docs/data#security You should be able use these in combination to se…

I still don't get how I, as a malicious (or curious) user with some form of write permission, would be prevented from doing the equivalent of opening up Firebug console and typing while(true){var p = new Post(); p.save();}

Presumably it is exactly the same as in any other web application--the save method is using an HTTP request under the covers, which must be rejected if the user is not authorized to perform that action.

Re: Parse launches JavaScript SDK: Parse for Websites

#39

Post by lux »

lacker wrote: post #32
lux wrote: post #29

Was just thinking this was the next logical move for Parse to really blow up. Nicely done too! I don't see examples of file handling through the JavaScript API though, did I just miss it?

Right now, we don't have binary data support (which includes file handling) in Javascript. It's a bit different than Objective-C and Java because Javascript doesn't have great native support for a binary data type. So we can't just expose the same API for binary data that we use for native SDKs. We're working on figuring out a really clean way to support binary data, though.

Good to know it's in the works! Definitely a messy problem with current browser limitations.

Re: Parse launches JavaScript SDK: Parse for Websites

#40

Post by falava »

Comparing the JS guide with the iOS and Android guides I see two absences:

1) Files

2) Facebook and Twitter users

May be that it's not possible to upload files or authenticate using OAuth using only the JS SDK, and without having and external server that secures the private keys?

Post reply on HN