A colleague of mine remarked that one of the things that bothered him about Go (and uC++, and to some extent, VHDL for that matter) was how much the languages resembled traditional imperative languages (like C). In particular, it was the cases where these languages did something that was different from C (i.e., "different from what the user expected") that caused him the most pain.

If the Flow language can figure out how to deal with this expectation, I think there might be something here.