Very colorful comments about Prism 2

This is a response to a quite colorful rant I received in email from Steve regarding a  Prism 2 post I did a while ago. I was so impressed by the literary quality of the piece that I thought it only fitting to publish.


The cleaned up version goes like this:


“ SO YOU ARE SAYING YOU TOOK AWAY THING THAT WERE IN THE OLD PRISM AND ADDED NEW THINGS IN THE NEW PRISM. SO WHATEVER I LEARN AND USED IN THE OLD PRISM I NOW HAVE TO FORGET AND GO BACK AND CHANGE FOR THE NEW STUFF. WELL HERE IS MY COMMENT TO YOU


F@%$ YOU SOB M#&$*R FU#$#R


JUST LIKE MISCROSOFT CREATE ONE THING SAY IT IS GREAT AND THEN CHANGE TO WHOLE DAMN THING


OH YEA ONE MORE THING YOUR MAMA IS A CHIMP”


Aside from the fact that the writing is a true masterpiece, I do have to point out that all the information is wrong.


First: Prism 2 internals changed but the outward impact to authors of existing Prism apps was minimal. The reason for the change was to allow full parity between Silverlight and WPF, which is something customers asked for, thus allowing you to recompile your Views and such to work in either platform. I am guessing you never actually looked at Prism to know whether that was the case.


I also am guessing you have no familiarity with actually how p&p works. For development of guidance like Prism 2, there is a customer advisory board heavily involved with the process and that would have screamed bloody murder had the decision been to completely break existing customers!


Second: I know for a fact that my mom is not a chimp.


Steve, please check your facts. Other than that keep up the good work. I think you have great writing potential!

This entry was posted in prism. Bookmark the permalink. Follow any comments here with the RSS feed for this post.
  • http://forevony.com cyberman

    :) These are the rewards that we hope for as developers

    I wonder if his second name was Daniels that night?

  • http://blogs.southworks.net/jdominguez Julian

    LOL, this is very funny! shame on you Glenn for the breaking changes in Prism 2 ;-)

  • addys

    ha! that made my day.

  • http://elegantcode.com Jan Van Ryswyck

    How one can become so open-minded is beyond me. A real diamond in the rough.

  • http://www.codebetter.com/blogs/glenn.block/ Glenn Block

    @Mike

    Glad to know that your Mom is not a chimp either.

    Glenn

  • http://www.codebetter.com/blogs/glenn.block/ Glenn Block

    @Darren

    I guess my encryption algorithm has a few kinks to get worked out. ;-)

  • http://www.codebetter.com/blogs/glenn.block/ Glenn Block

    @Ben yes we aim to stifile, and yes we are perfect ;-)

  • http://www.codebetter.com/blogs/glenn.block/ Glenn Block

    @Mike

    I am sure it wasn’t intentional. But glad, that you can grab the source and work around it.

    BTW, if you have any fixes, you might want to upload them to Prism contrib.

  • http://www.codebetter.com/blogs/glenn.block/ Glenn Block

    @Joe Good to know, I’ll let the guys know on the Prism team. We are looking at further MEF integration possibilities in the future.

  • http://www.codebetter.com/blogs/glenn.block/ Glenn Block

    @Derek thanks for backing me up :-)

  • Darren Kopp

    you censored the word “mother”?

  • http://flux88.com Ben Scheirman

    Yeah, Glenn, didn’t you know? You guys should stifle improvement at all costs! Microsoft obviously bakes in the PERFECT FLAWLESS design the first time, so why bother to change it? ;P

  • Mike Strobel

    On the whole, I’m pretty happy with Prism V2. The compatibility breaks were minimal and quick to resolve. My only complaint is that the P&P team doesn’t seem to pay much attention to the CodePlex Issue Tracker. There are a few issues that I’d like to see resolved. Thankfully, the open source nature of Prism allows me to correct these issues myself for the time being, so thanks again for that :).

    And for the record, my mother isn’t a chimp either.

  • http://blogs.windowsclient.net/joeyw Joe

    Nice !
    Anyway, I would be interested in the policy of breaking changes going forward. For example, I wouldn’t be too set against a breaking change in PRISM if it were to adopt some of the MEF constructs that I understand will become part of .NET 4.
    I would rank design and integration with .NET higher on the priority list to backward compat. But that’s just my opinion….

  • http://meandmycode.com Stephen

    Wow, what a freak..

  • http://www.gamemax.org Mladen Mihajlovic

    That, and also chaging the WPF namespace to Presentation…

  • http://ctrl-shift-b.com Derek Greer

    LOL! To add to this, I just recently recompiled some examples I did with v1 and all I recall having to do was to account for the new module catalog stuff.