5 ms·

Nice job, guys. I love this architecture. This looks a lot like my dream stack for future web work. Would love to hear some more about the "bleeding" experienc

Nice job, guys. I love this architecture. This looks a lot like my dream stack for future web work. Would love to hear some more about the "bleeding" experiences you've had.

dodger 15y ago
Socket.io: https://github.com/LearnBoost/socket.io/issues/686 https://github.com/LearnBoost/socket.io/issues/686 MongoDB (on FreeBSD): https://jira.mongodb.org/browse/SERVER-3927 https://jira.mongodb.org/browse/SERVER-3927 Redis: https://github.com/antirez/redis/issues/91 https://github.com/antirez/redis/issues/91 . . . are a few.
- jashkenas 15y ago
  dodger: I'd be curious to know where y'all bled over CoffeeScript or Backbone, if you don't mind sharing.
  - dodger 15y ago
    Actually, those have been great (and thank you for making them)! We had an outage during beta because somebody forgot to wrap an array comprehension assignment (CoffeeScript) and we didn't test right. Backbone has been really good, and while we had some complaints, I think many have been resolved in more recent versions - we're on something ancient.
    - robocat 15y ago
      > "we're on something ancient" Isn't that one of the major drawbacks of using a bleeding edge Tech Stack? Albeit mitigated by choosing to use code that is easy to comprehend/maintain (like backbone!) What do you think you will do? E.g. With backbone: Merge up, status quo -- maintain your branch, change libraries, or something else?
      - dodger 15y ago
        Agreed, it made some necessary, non-backward-compatible changes as a result of being such a young project. I think it is likely that we will upgrade to a newer version soon.
- slewis 15y ago
  The MongoDB one is a real cliffhanger. What happened?
  - dodger 15y ago
    We worked around the bug (which only happened when we were doing REALLLY long queries when we disconnected a client) and moved to Linux, where the bug does not exist. Awesome sysadmin Tim GDB'd into Mongo and figured out that it was an issue with SpiderMonkey, fixed in later versions.

Nice job, guys. I love this architecture. This looks a lot like my dream stack for future web work. Would love to hear some more about the "bleeding" experiences you've had.

dodger 15y ago

Socket.io: https://github.com/LearnBoost/socket.io/issues/686 https://github.com/LearnBoost/socket.io/issues/686 MongoDB (on FreeBSD): https://jira.mongodb.org/browse/SERVER-3927 https://jira.mongodb.org/browse/SERVER-3927 Redis: https://github.com/antirez/redis/issues/91 https://github.com/antirez/redis/issues/91 . . . are a few.

jashkenas 15y ago
dodger: I'd be curious to know where y'all bled over CoffeeScript or Backbone, if you don't mind sharing.
- dodger 15y ago
  Actually, those have been great (and thank you for making them)! We had an outage during beta because somebody forgot to wrap an array comprehension assignment (CoffeeScript) and we didn't test right. Backbone has been really good, and while we had some complaints, I think many have been resolved in more recent versions - we're on something ancient.
  - robocat 15y ago
    > "we're on something ancient" Isn't that one of the major drawbacks of using a bleeding edge Tech Stack? Albeit mitigated by choosing to use code that is easy to comprehend/maintain (like backbone!) What do you think you will do? E.g. With backbone: Merge up, status quo -- maintain your branch, change libraries, or something else?
    - dodger 15y ago
      Agreed, it made some necessary, non-backward-compatible changes as a result of being such a young project. I think it is likely that we will upgrade to a newer version soon.
slewis 15y ago
The MongoDB one is a real cliffhanger. What happened?
- dodger 15y ago
  We worked around the bug (which only happened when we were doing REALLLY long queries when we disconnected a client) and moved to Linux, where the bug does not exist. Awesome sysadmin Tim GDB'd into Mongo and figured out that it was an issue with SpiderMonkey, fixed in later versions.