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

Show HN: Firebase, a scalable real-time backend

firebase.com

Post reply on HN
Print view View original

91–100 of 148 posts

Re: Show HN: Firebase, a scalable real-time backend

#91

Post by aidenn0 »

nick_urban wrote: post #90
pron wrote: post #74

Earlier quoted context omitted.

You could say that just about any software development platform. If it makes building software easier, it makes competition easier. And if building apps is easier, it really doesn't matter what stack your app uses - it's going to get easier to "clone", so you may as well use whatever platform gives you the best results. Other than that, you could either make your business, rather than your technology, more competitiv…

It's not that client-side applications are easier to reverse-engineer. If the application is all client-side, it can literally just be downloaded and reused by a would-be competitor.

which violates your copyright.

Microsoft Word is entirely client-side so it too can literally just be downloaded and reused by a would-be competitor.

Re: Show HN: Firebase, a scalable real-time backend

#92

Post by codergirl »

vvnraman wrote: post #68
pkrein wrote: post #4

I used Firebase to build thereelbox.com, and enjoyed it thoroughly. It took 2-3 hours from starting into the documentation to completed/nobugs/pushed to production. Credit for that speed goes entirely to Firebase. TheReelBox uses Firebase as a sort of API caching layer. This protects against rate limiting on the Rotten Tomatoes API, decreases request time by caching queries to the Fandango-via-YQL API, and eliminates…

Wow !! As a movie buff myself I think I'll be vising you site almost everyday now. This is what I used to do before: - Go to www.imdb.com - Click on 'See more movie showtimes' at the right. - On the next page, click on the 'Favorites' tab to choose a theater. - Go to maps.google.com and plan the route to the theater. This is definitely going to save me at least a few hours every week while I check which movie is play…

You can also type 'movie showtimes' into google and there is a nice interface with maps which shows movies and which theatres they're playing at.

Re: Show HN: Firebase, a scalable real-time backend

#94

Post by felixchan »

smoody wrote: post #70

Here's my big concern: If my entire app is client-based JavaScript, wouldn't that make cloning my app as simple as copying all of the JavaScript and other asset files and then associating them with another firebase account -- perhaps modifying them some so they dont't get banned? It seems like it lowers the barrier to competition a bit too much for me.

I think you're thinking a little too short-term here. It seems like a jump in technology that could completely change the way people build apps.

Re: Show HN: Firebase, a scalable real-time backend

#95

Post by pilom »

aidenn0 wrote: post #91
nick_urban wrote: post #90

Earlier quoted context omitted.

It's not that client-side applications are easier to reverse-engineer. If the application is all client-side, it can literally just be downloaded and reused by a would-be competitor.

which violates your copyright. Microsoft Word is entirely client-side so it too can literally just be downloaded and reused by a would-be competitor.

Downloading Microsoft Word does not include all the source code in addition to the application.

Re: Show HN: Firebase, a scalable real-time backend

#96

Post by BHSPitMonkey »

felixchan wrote: post #94
smoody wrote: post #70

Here's my big concern: If my entire app is client-based JavaScript, wouldn't that make cloning my app as simple as copying all of the JavaScript and other asset files and then associating them with another firebase account -- perhaps modifying them some so they dont't get banned? It seems like it lowers the barrier to competition a bit too much for me.

I think you're thinking a little too short-term here. It seems like a jump in technology that could completely change the way people build apps.

You should work in their marketing department.

Re: Show HN: Firebase, a scalable real-time backend

#97

Post by [deleted] »

aidenn0 wrote: post #91
nick_urban wrote: post #90

Earlier quoted context omitted.

It's not that client-side applications are easier to reverse-engineer. If the application is all client-side, it can literally just be downloaded and reused by a would-be competitor.

which violates your copyright. Microsoft Word is entirely client-side so it too can literally just be downloaded and reused by a would-be competitor.

[deleted]

Re: Show HN: Firebase, a scalable real-time backend

#98

Post by jchrisa »

felixchan wrote: post #94
smoody wrote: post #70

Here's my big concern: If my entire app is client-based JavaScript, wouldn't that make cloning my app as simple as copying all of the JavaScript and other asset files and then associating them with another firebase account -- perhaps modifying them some so they dont't get banned? It seems like it lowers the barrier to competition a bit too much for me.

I think you're thinking a little too short-term here. It seems like a jump in technology that could completely change the way people build apps.

Glad to see interest in the idea. It's not much different from what people have been doing with projects like http://couchapp.org or http://unhosted.org/ for some time.

Once you have a basic HTTP database API, you can do most of an app in client-side JS. Security is the hardest part to get right. In CouchDB we've tried to follow the web security model when it makes sense (single origin policy, oauth, etc).

CORS and WebSocket are both changing the web model, so it's not surprising to see the idea of a simple data API catching on as the web gets more power. Can't wait to see where this goes.

Post reply on HN