Great to see Erik again :) Why did MS fire him?! I wanna know all the details please ;D I am reading through G.E.B at the moment and all this stuff resonates beautifully with ideas shown there...It is like everything has been invented already, except it has not, because we can still come up with new ways of reusing old ideas, by applying concepts deeply rooted in mathematics, which in itself is incomplete and instantly evolving according to Godel and others ;) Thanks for the session!

@RT1138: I never left C9 (I'm a lifelong Niner, man), but I am no longer on the C9 team... I make content infrequently, but always love to get the chance to when I can.

Yes, Bart is employing Rx in most everything he does (including Bing's Cortana), but I don't think you can or even should compare Bart to Erik in terms of Rx "ownership"... However, since Erik is no longer at MS, you could say that Bart is the keeper of the Rx flame, though even that is not quite accurate given that MS Open Tech actually maintains the technology in partnership with the community (it's open source, after all)...

You'll see Bart again on C9 once we get a long technical interview through legal...

@mdonatas:I agree and i do not understand this. I always enjoyed to watch Erik's interviews on C9, but especially his Haskell series. I am myself european and to say so i personally f.... on f-bombs, but after having worked more than a decade for ms i do not quite understand this aggressive approach towards ms in this talk.

@mdonatas: @wandreas: As you know, Erik is fueled by passion and therefore emotion. He has resentment towards MS because of how the relationship ended (it was a breakup more than anything else, an unfortunate turn of events that did not lead to a firing. He left on his own accord, but the circumstances gave him little choice - in his mind - but to leave. That's all I will say on the matter.).

For any given talk, you can't control what a speaker says and how it is said. If Erik felt his commentary regarding MS was appropriate, then what are we to do? Not ship the talk because our feelings may be hurt? I don't think so. We're big boys and girls and can handle a little jibing. Erik has the right to feel as he does. Sure, he made a few offhand comments about MS, but the vast majority of his talk was not about MS... People are free to express their opinions and Erik's feelings towards MS are his own. They do not represent some sort of absolute reality...

Microsoft is full of people who talk about code and also code. I don't know many people working on products who don't code, regardless of their job title. PMs on engineering teams are often writing code to verify the soundness of their ideas. Testers are software developers.... I don't agree with the statement Erik made about how everybody in Silicon Valley who talks about code also codes, but how that is not the case in Redmond... This doesn't mean I will have it edited from the talk. Hopefully, after all these years, you understand that we don't do that on Channel 9.

I think Erik is totally correct! He did a lot to MS, (co-)created many cool and innovative things like LINQ and Rx, and the company didn't recognise his efforts properly. Now, any platform have Reactive stuff - look at the push made by Typesafe with the Reactive Platform.

I think MS isn't marketing (or don't care) masterpieces like Rx or F# properly, because they aren't "sellable" as cash cows. Therefore, others will be THE players in Functional and Reactive stuff, sad but true...

@Fabio Galuppo: Don't drink too much of the typesafe coolaide :) While I love what they are doing, I am not so fond of their attempt to pervert associations like Reactive == Actor, Actor == Typesafe therefore Reactive == Typesafe. Reactive is much bigger than that. Rx plays his part, which we are all super grateful to Erik (and Bart et.al) for giving us. Rx is cross platform now thanks to continued work from MS, Erik and Guys like Ben at Netflix.

Another point, this is a canned presentation. It is a well planned and executed and has been performed at other conferences. The firing analogy works well for it's purpose (comedy, marketing stunt and conveying knowledge). In my experience, off stage Erik is a very sweet and passionate person.

While I found this talk interesting, I did not enjoy it due to the frequent unpleasant, cynical, unfunny, and sarcastic remarks.

For me, being rude about a large company is one thing, but singling out particular people for ridicule is quite another: derisively including Steve Ballmer in his actual code examples is astonishing for someone who should know better and has always managed to behave himself here previously.

But maybe I'm just no fun. I'm from the UK, so don't mind "f***" (that word is frequently used around the office). Interesting to know that in the US it is a faux pas.

On the technical side I found the modelling of getters and setters as pull and push collections (IE/IO) interesting. In a previous C9 video I believe Erik mentioned his affinity for "first-class" constructs. Mapping getters and setters into these interfaces make them more first-class in a way. So for example one could subscribe to an accessor and listen to "settings" (or "gettings" too, actually). I love that generality.

I think just based on the general definition of "reactive" that the push idea of observer is more accurate than side-effect. I can understand that Erik may have other ideas to it and prefer a change, but I'm not so sure "side-effect" is better.

Both definitions carry a negative connotation in context; however, "side-effect" has a greater negative weight then "reactive".

If I had any opinion that mattered, as if... I would say some mathematical terms could be more relevant to describe this evolving pattern, sort of like "state functions" and "integrals"... but, for me.. reactive is fine.

Remove this comment

Remove this thread

Comments Closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums, or
Contact Us and let us know.