Neat, I already use mattt's CLI tool for interfacing with the Apple dev site: https://github.com/mattt/cupertino
Helios
51–60 of 69 posts
Re: Helios
#52Re: Helios
#53This is really great. A massive limitation of Parse.com is with their Javascript SDK - you have to expose your app keys to the client and the SDK doesn't work at all on any version of IE unless you have SSL enabled.
2) Wouldn't any similarly-situated Javascript library face the same problems, with Access Control Lists probably being the most practical solution?
3) Moreover, with any mobile backend, you must assume that the keys that ship within the code of your native app will be public. So you should be using Access Control Lists if you're using the iOS SDK, for example.
Re: Helios
#54Re: Helios
#55But I worry about how it would hold up in terms of performance, given this recent benchmarking fest featured on HN. http://www.techempower.com/blog/2013/03/28/framework-benchma...
Re: Helios
#56Re: Helios
#57Off topic: The ultra light custom fonts a lot of websites use nowadays (looks like "Bariol" on this site), do they look bad to anyone other than me? Both in Firefox and Opera (Linux) many of the lines are invisible or barely visible (example: http://i.imgur.com/Yk0Q83G.png ). In Chrome they look a little bit better.
Re: Helios
#58This looks awesome - a Parse.com you can deploy yourself!
Re: Helios
#59Re: Helios
#60I've been debating using something like Parse or Azure as a backend, and this looks like a nice alternative as I'm usually a roll-your-own-solution kinda guy. But I worry about how it would hold up in terms of performance, given this recent benchmarking fest featured on HN. http://www.techempower.com/blog/2013/03/28/framework-benchma...