Asus tells us it hopes to see this slate's battery life increase with the transition to Sandy Bridge mobile processors, and it apparently has a battery upgrade in the works, too. Together, those changes could add up to roughly six hours of battery life in a future version of the slate, which would be a very helpful improvement.
Nice lecture, but I do have a suggestion for Ralf. In approximately the first half of the lecture, I found a few transitions to the next slide or point quite fast. Adding a short pause of a second or so might give the viewer a little bit of room to breathe and process all the information.
Other than that, nice work and I'm looking forward to your next C9 lecture (whenever that may be).
I do think there is still more discussion to be had on the x= x + 1 problem Erik mentioned on Actor pattern. Do you solve it via convention, static rules, or some other way? Guess would need to list all the use cases and sticky points and toss spegetti at it.
From what I've understood is that Herb suggests that you design your API in such a way that it allows your users to express as much as possible in a single call or message. In the x=x+1 example, you don't want the user to first send a message to get x, compute the new value of x and then send the new value of x back to the actor. It's probably preferable to have the user use only one message in total to update x. You could think of an "IncrementX" message, or perhaps more generally, a "ModifyX" message which contains a lambda**.
So I've watched the video and been pondering about something. Bart, you use Ana instead of Unit (or Return). As you explained in the video, you can define Unit in terms of Ana. So far's everything fine.
The thing I've been pondering about, can you always define Ana for each monad M?