[mikewarot]

1> Because no current OS is based on capabilities, no current OS can be trusted to secure an application. This void is being filled with containers and virtualization as a stopgap. Eventually, capability based operating systems could fix this, and become a trillion dollar market.

2> There should only be one logical task per line of code. The right density is that of basic or pascal. Clever use of compound assignments, macros, etc. cost more than their worth in the long run. It makes code harder to read, and easier to misunderstand, even when you're writing it.

3> Moore's law gave us a nice boost in hardware, but the ride is coming to an end. If your software doesn't distribute across cores, you're going to be stuck in the slow lane compared to that which does.

4> Accounts with usernames and passwords are going away. Capability tokens that can be revoked and renewed are going to be the next big thing. Think Flickr's guest pass to look at an otherwise private photo album, for example.

[0x445442]

Agree with point 2. But 2&3 are somewhat orthogonal.

[mikewarot]

Well, the written density of source code has to match the impedance of the programmers that deal with it, not the computer, which deals with binary executable just fine.

It seems to me the more clever you are, the harder it is to understand and debug code. Breaking things down into logical steps, but not too far, works best for me, and I suspect, but can't prove, the general case as well.