3 ms·

The main reason you might want to use Firepad instead of Etherpad is if you don't want to run the server-side piece of Etherpad. For example, if you're stack is

The main reason you might want to use Firepad instead of Etherpad is if you don't want to run the server-side piece of Etherpad. For example, if you're stack is different than theirs it might be a pain to set up a special server environment just for the collaboration portion of your app. Firepad is fully client-side code, so there's no server software for you to set up. The other big reason you might use Firepad is to get all of the other goodies that Firebase provides, like the automatic scaling, Forge debugger, declarative security, etc.

kevinr 14y ago
So, when you say it's "fully client-side code" -- what that looks to me to mean is not that it's not talking to a server somewhere, but that it's talking to Firebase's servers rather than my servers. Is that correct?
- akkishore 14y ago
  Right, communication to Firebase happens with its API.
  - unhammer 14y ago
    Can you run it without it communicating with Firebase? (If not, how is that better than having it under your own control?)