/prog/ is really fast

when you read it once a week

>>4
No-no-no. Design software, not hardware.

1. An object receives a message to screw some billions of numbers around.
2. The object runs the whole numberfuckery internally with efficient arithmetic primitive operations on unboxed numbers.
3. The object sends a message with the result.

See, it could be performant. What's the problem with this scheme besides the lunatic ideas that "in an OO language everything must be an object" and "you must be able to redefine CAR and CDR"?