Threading, finally ?
Posted: Tue Mar 23, 2010 5:15 pm
Althought the event-based nature of RunRev allows you to do pretty amazing stuff, there are some things that you just CANNOT do without threading support (turning blocking call into non-blocking for example). I know that implementing threading (correctly) is not a small task, but the event-based message-passing nature of Rev should help.
I know i can spawn external apps to delegate the tasks to, but this is a kludge. And I know that directly dealing with threads is hard-to-get-right, but a few languages managed to build a set of abstractions that keep the programmer away from messy implementation details and just allow them to reap the benefits (zero-copy message-passing etc.) of a threaded VM / runtime-system implementation (ie. Haskell, Erlang etc.)
Reaching for a C/C++ compiler and writing an extension (for every friggin' blocking call/API) just doesn't cut it for me (I'll rather stomach the bit more static development model of other langs if they give me all the other goodies i need).
I know i can spawn external apps to delegate the tasks to, but this is a kludge. And I know that directly dealing with threads is hard-to-get-right, but a few languages managed to build a set of abstractions that keep the programmer away from messy implementation details and just allow them to reap the benefits (zero-copy message-passing etc.) of a threaded VM / runtime-system implementation (ie. Haskell, Erlang etc.)
Reaching for a C/C++ compiler and writing an extension (for every friggin' blocking call/API) just doesn't cut it for me (I'll rather stomach the bit more static development model of other langs if they give me all the other goodies i need).