4 ms·
Funny--he started out "after another Campfire outage this week", I thought the post was going to be about the unreliability of Campfire, its platform (ruby, das
by stephen 16y ago
Funny--he started out "after another Campfire outage this week", I thought the post was going to be about the unreliability of Campfire, its platform (ruby, dash of C, AFAIK), and the uptime issues causing user-hostility amongst 37signal's customers.
Which was going to be (and still is) ironic since BankSimple is likely using the same technology stack.
After being down voted: so Alex can call all AIR developers lazy because they don't want to leave their comfort zone and write native apps, but I can't insinuate the same thing about 37signal's not wanting to leave their Ruby comfort zone to make a reliable messaging app? Oh, right, we hate AIR, but love Ruby. Sorry, I missed that there was a double standard. :-)
- al3x 16y agoWe're using a bit of Ruby, but not C, and mostly Scala and Clojure. Either way, I think reliability is a process thing, not a technology thing.
- stephen 16y agoYes, true. I am admittedly showing my bias. Thanks for the reply.
- aaronblohowiak 16y agoI meant to up vote you, but missed (iPad.) Can you elaborate on heat you mean by process and not technology?
- cmelbye 16y agoWow, really? First of all, 37signals DID step out of their comfort zone by using Erlang rather than Ruby for their backend to handle sending chat messages out to clients. Secondly, I was under the impression that BankSimple was essentially using Ruby on Rails for their front end, and Scala and other JVM-based languages on the backend. Finally, how is Ruby at all related to the Adobe AIR client in question?
- stephen 16y agoThanks for the correction--I last used campfire pre-erlang and missed the switch: http://37signals.com/svn/posts/1728-nuts-bolts-campfire-loves-erlang http://37signals.com/svn/posts/1728-nuts-bolts-campfire-love...