I guess that real-time has lost its original meaning in computing.<p><a href="http://en.wikipedia.org/wiki/Real-time_computing" rel="nofollow">http://en.wikipedia.org/wiki/Real-time_computing</a>
Fantastic. Pusher is an awesome product that eliminates the headaches associated with building a real-time product. I'll never build a chat with polling again. I use it for my website and haven't had any problems (well one, but it was mostly caused by my inexperience with rails)<p>The best part is the pricing, especially for startups. 20 concurrent users for free is a big number. Compare it to something like MailGun, and it seems like $20/month gets you a lot more value.
Quick question: for someone or a team already extremely well versed in Node.JS, HTML5 and Socket.io, where the core product is already real-time by design from the ground up (rather than a legacy HTML page-based experience that needs to be "up-realtime-d quickly") -- should they be looking into Pusher and how would it help them?<p>I really mean folks who diligently code their own server sides and client sides "completely" (utilizing OS libs of course) by themselves and work on a for-local-installation product that should not require www/online connectivity (think non-public intranet servers) to run its core real-time functions -- should they be looking at Pusher at all? Or is this "just a quick external JS lib to add a chat, drawing or puzzle game to your popular HTML 4 website"?
I've used Pusher on a couple apps and it was extremely simple and painless. However, I've found that it's not that much more difficult to roll my own real-time solution using juggernaut/socket.io/node.js. What I lose is the support, but what I gain is obviously the cost savings.
I see the founders are also doing <a href="http://new-bamboo.co.uk/" rel="nofollow">http://new-bamboo.co.uk/</a><p>if Pusher got funding, does that mean they have to leave new bamboo and panda?