5 ms·
Totally agree. Since when did a work queue/thread pool thing become anything beyond intro to systems work? Furthermore, I don't know where everyone gets off sa
by lzimm 16y ago
Totally agree. Since when did a work queue/thread pool thing become anything beyond intro to systems work?
Furthermore, I don't know where everyone gets off saying erlang is so fast either: I'm not sure where things are now, but last time I checked, their scheduling algorithms were leaving quite a lot on the table, standing to benefit quite substantially from even the most basic operations and logistics knowledge.
- revoltingx 16y agoUgh, because you'd have to be pretty stupid to try to implement what Erlang/OTP has yourself. Yeah it's easy, but it'll get pretty hairy once you integrate hot-code updates, complex/simple CPU usage, load distribution, etc (i.e. you can write your app single threaded, then run 4 erlang VMS and distribute the load between all four of them.) The ability to easily swap between parallel and sequential functions easily, cross-process/cross-network seamless communication, etc. All of this without ever having to restart the VM or having 'downtime.' The point of Erlang is that it makes all of this so easy that you don't even think about it. It's the scripting language of parallel computing. You can rapidly prototype the app using the built-in tools and fine-tune whatever needs to be refined with C or better parallel algorithms or both.