As to the demo, this is the ASUS Eee Slate 12" Tablet. I would wait for the Sandy Bridge version which should be coming out soon, but this one features about 4 hours battery life.
Do you have any sources that indicate a Sandy Bridge version will be coming out soon?
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?
Currently watching the video and it's nice so far.
Also, when Bart used the word "aspect" in his explanation of what a monad is, I was reminded of the following paper: On the relation of aspects and monads.
Jensen Harris Walks Us Through the Windows 8 UI
Sep 13, 2011 at 10:53 PMI am really curious how Win8's UI will deal with pen input, or even better, pen+touch input.
C9 Lectures: Greg Meredith - Monadic Design Patterns for the Web 4 of n
Jul 29, 2011 at 2:01 AMUsing Microsoft Office on a Tablet PC touch screen
Apr 01, 2011 at 5:34 AMThe Fujitsu Q550 uses N-Trig technology instead of Wacom for pen input though. For some people this might be a reason not to buy the Q550.
Using Microsoft Office on a Tablet PC touch screen
Mar 30, 2011 at 2:49 AMDo you have any sources that indicate a Sandy Bridge version will be coming out soon?Never mind, found something on this page:
C9 Lectures: Dr. Ralf Lämmel - Going Bananas
Jan 22, 2011 at 7:38 AMNice 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).
E2E: Herb Sutter and Erik Meijer - Perspectives on C++
Jan 16, 2011 at 1:42 AMFrom 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**.
(** Hmm... are C++0x lambdas serializable?)
Bart De Smet: MinLINQ - The Essence of LINQ
Jan 02, 2011 at 10:43 AMSo 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?
Bart De Smet: MinLINQ - The Essence of LINQ
Jan 02, 2011 at 9:36 AM@AdamSpeight2008:
The problem is that operators are static in C# (Shared in VB), so you are pretty much forced to multiple overloads.
Here's something I found about generic operators written by Marc Gravell and Jon Skeet: http://www.yoda.arachsys.com/csharp/genericoperators.html
Bart De Smet: MinLINQ - The Essence of LINQ
Jan 02, 2011 at 4:50 AMGreat way to start the year (currently half way through the video).
@Bart: I'm amazed by your simple IE->IO->Amb->IE roundtrip example. It is concise yet clear, demonstrating the importance of orthogonality.
Bart De Smet: LINQ to Z3
Nov 26, 2010 at 9:48 AMCurrently watching the video and it's nice so far.
Also, when Bart used the word "aspect" in his explanation of what a monad is, I was reminded of the following paper: On the relation of aspects and monads.
See more comments…