"Problems arise when in the quest for simplicity important distinctions are hidden. In programming languages this usually comes up when discussing performance. The distinction between primitive and object types really matters if you care about speed. Scala gets away with this for the most part through clever compilation in both the Scala compiler and Hotspot, but writing high performance code can still be something of a dark art."
How might/can/will Bit-C strive to prevent there being an inflection point where the developer has to say, "ok, i can't get the performance i need like this, now i have to start noodling over the weird details and ripping up my nice abstractions to eke out the performance i need. ... come to think of it, this is teaching me to just go back to my c/++ roots."? _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
