Any blog posts that start with "The future of..." could sound a bit frightening. In this case, it might even be true (gasp!). With R3 storming ahead and REBOL/Services proving itself worthy through DevBase, I'm not sure what place Rugby has at this time.

Furthermore Rugby will definitely not be compatible with R3 as the entire port handling system has changed and HTTP scheme has been rewritten from scratch.

The original author, Maarten Coopmans, has chosen not to pursue further development of it.

Please note that I will of course continue to serve the sources for Rugby. They will not go away. Some annoying bugs still remain, and one of these bugs is a deep one that occurs in R2 ports which causes R2 to hang on sending information from the Rugby client to the Rugby server in very specific cases. I've not had the time or the inclination to fix this bug, as it's very difficult to track down. There are also problems with sending words and objects across a Rugby connection and I've not managed to fix those properly either. These things can be fixed in one place and then cause trouble in another place.

Rugby is very nice for quick RPC systems, but it scales only so much, so use it if you want some simple single-threaded RPC stuff. For more complex high-performance multi-threaded fancy networking, wait for R3.