4 ms·
We have Ruby, Python, Go, C, Node, Perl, Backbone and maybe a few others I'm not remembering right now. When you're building distributed systems, you pick the
by aspir 12y ago
We have Ruby, Python, Go, C, Node, Perl, Backbone and maybe a few others I'm not remembering right now.
When you're building distributed systems, you pick the right tool for the job.
Edit: And Assembly: http://youtu.be/zrSvoQz1GOs?t=15m44s http://youtu.be/zrSvoQz1GOs?t=15m44s I'd actually recommend the entire talk.
- Kiro 12y agoStill, why so many different? Must be really messy.
- aspir 12y agoIt definitely can be, since it's an infrastructural distributed system, but it's all unix when you break it down.
- alexgartrell 12y agoYou can't just throw out a platitude like "it's all unix when you break it down." That doesn't actually make any sense. When you use a bunch of different languages the primary difficulty you run into is interop. Some languages work well together by default and interop is easy, but this is almost never the case. Generally you're stuck making the decision between easy interop (RESTful APIs or your favorite RPC framework) and fast interop (JNI, swig, etc.). So how do you guys actually deal with interop, other than to limit the need for it?
- clubhi 12y agoAre you guys building a business or just trying to have fun?
- aspir 12y agoWe're doing all right: www.fastly.com/customers
- deleted 12y ago[deleted]