3 ms·
See my other reply though: it's not just about the API, which is nice, but about getting the architecture right. It does make the system more robust, but it re
by davidw 10y ago
See my other reply though: it's not just about the API, which is nice, but about getting the architecture right. It does make the system more robust, but it requires more thought and planning.
- im_down_w_otp 10y agoSure. Once you cross that barrier, you now have unlimited ammo and all the feet that ever were or will be, so you have to be a lot more diligent about what you're doing.
- davidw 10y agoI guess my point is that in, say, Tcl, you pretty much just worry about calling out to the C code and if it takes 2 seconds to process an image or whatever, so be it. You merrily go about your business once the call returns. In Erlang there's more to think about.
- im_down_w_otp 10y agoI think that's technically true in Erlang as well... it's just that it makes all the other stuff that people expect from Erlang to mostly stop working smoothly. :-)