Tell me /prog/, why are you still using lisp and scheme when you can use C++ with Object Oriented and Imperative styles. How are you supposed to make a usable application if you can't use state?
>>37
Actually it does. A big part of why Ruby is fucked up is that standard practice for virtually everything is to manipulate the prototypes. It's a language built on bad practice. The way Ruby does it is about as reasonable as boxing your results in exceptions instead of using return.