Sanjay

That MS decided to totally blow it up in .NET 4.0. (weblogs.asp.net link, S/O link).  Yes, that’s right, they are totally re-writing WF 4.0  from the ground-up.  As the first link states, this could be for any number of reasons including lack of adoption and the perception that WF is just too complex – which I happen to agree with.  3.0/3.5 workflows will still work, but only on the 3.0 runtime. 

On the one hand, I have to give some credit to MS for basically saying “Hey guys, we effed up and we’re gonna scrap this…”, and yet, on the other I have to assume it’s a little embarrassing to have to do something like this. 

BTW, Is this old news?  How did I totally miss the memo on this?

Share this post :

 

Technorati Tags: Workflow,.NET

Was doing some research this morning, as usual, and came across a post from Giulio Bai on jQuery performance tips.  A lot of his tips are things I’ve heard elsewhere (no offense!), but one that I haven’t seen anywhere and for some reason surprised me is that using a the JavaScript provided for() loop is considerably faster than using jQuery’s each() function.  In fact, it can be several orders of magnitude faster depending on what you’re doing.  Interesting. 

Link to his post