panduwana

So it needs taxpayer subsidy just to be on par with fully-private Falcon 9? Seems like it loses before the match even begins.

In the linked article it is said that "According to prior research, only some 13% of values are used more than once". So based on the research on which Mill is based on, your example and that "instruction can use any result on the belt" is actually minority case.

As for scheduling my proposed store-addressed belt: you perform as many operations in parallel, then for each operation find the other operation that depends on the former's operation result, calculate the distance between them and assign it as the former's store address. The compiler has more work to do yes, but not "much more difficult".

If the belt operation can be changed from the current "take any two items on belt, process them, put the result to the front of belt" to "take two front-most items on belt, process them, put the result anywhere on belt", we can save some bits and make shorter instructions (good for mobile):

currently: OP load-address-1 load-address-2 // output is always put at belt's front

to: OP store-address // inputs are always 2 frontmost items on belt

What country?

Or virgins?

Sure. RBTree in C is that ugly. Take your time.

> Now why is this? It's because web apps offer a significantly poorer user experience across the board.

That is true today, but to say the issues can't never be solved is a bit of stretch:

- Speed issue: NaCl.

- Standard widgets: HTML5 already have input type=datetime, color picker, address book, and many more.

- Animation: WebGL.

- GPS: Geolocation API is available today on most browsers.

- Sensors: Accelerometer API is available today on some browsers.

Now I'm not saying that web app will certainly become the norm, but it's not impossible.

How did you learn about Clojure on GAE? What editor/IDE do you use (for Clojure)?

It's no longer AMD's fab, they spinned off their manufacturing arm as a new company named "Globalfoundries".