the discussion with jaron lanier recently on how to improve software development is very interesting. from what i can tell, his main issue with the current practices is that a bug in one area of code can have very broad repercussions on other areas of code. i think that many cases, this is because of hardware issues - a single CPU is responsible for executing a bunch of different code, and if one bit of code goes haywire, it screws the utilization of the CPU up. ideally, each bit of executing code has its own executor (virtual processor) that is immune to the misbehavior of other virtual processors. this would go a long way to enabling robust systems. and i don't just mean one virtual processor per *program*, i mean one virtual processor per *method*. in fact, the new language i've been working on basically assumes this model of execution.
1:35:20 AM 
|
|
