http://blogs.msdn.com/gblock/archive/2007/12/07/if-acropolis-is-no-more-what-s-our-commitment.aspx
CAB? Acropolis? CAB? Acropolis? CAB? Acropolis? CAB? Acropolis? CAB? Acropolis?
It looks like Acropolis may be going by the wayside, and the Patterns and Practice Group has decided that, for today, they will refocus on CAB.
This is precisely why we build our own .NET frameworks in my investment bank. Because, we need a high quality framework that has some domain knowledge of what capital markets needs. Goldman, Wachovia and Morgan Stanley have done the same.
And, this time last year, Microsoft came in and tried to get us to adopt CAB, and the week after that, they told us that Acropolis was the new flavor of the day. Thank the lord that we were focused on a mission to build what we wanted and needed, without all of the background noise from Microsoft. (Sorry Joe...)
©2007 Marc Adler - All Rights Reserved
Showing posts with label CAB. Show all posts
Showing posts with label CAB. Show all posts
Tuesday, December 11, 2007
Saturday, June 16, 2007
The Flavor of the Month is Acropolis
Now, after touting CAB for a few months, Microsoft has announced Acropolis.
A few months ago, the Microsoft DPE team came to me and tried to dissuade us from developing our .NET client framework in favor of using CAB. However, during those conversations, the word Acropolis came up a few times.
Now that Microsoft is touting Acropolis, what has become of CAB? Will this now be an officially supported framework (remember ObjectSpaces?). What about all of the financial service developers that committed to CAB? And, now you have some Microsoft people telling us that CAB was never officially supported by Microsoft, that it was developed by a small group of independent developers in some far off country that nobody ever heard of!
One thing about developing your own framework and making it a standard in the company is that it won't turn into a flavor-of-the-month entry. Goldman lead the way with OCEAN. Wachovia has OneSource, and Morgan Stanley has FidSharp and Concord. And we have ours. And, our companies tell our developers that they should use it.
No doubt that Acropolis will be "better" than CAB, and will have learned lessons and anti-patterns from CAB usage. Only, what will Microsoft come out with in another 6 months?
©2007 Marc Adler - All Rights Reserved
A few months ago, the Microsoft DPE team came to me and tried to dissuade us from developing our .NET client framework in favor of using CAB. However, during those conversations, the word Acropolis came up a few times.
Now that Microsoft is touting Acropolis, what has become of CAB? Will this now be an officially supported framework (remember ObjectSpaces?). What about all of the financial service developers that committed to CAB? And, now you have some Microsoft people telling us that CAB was never officially supported by Microsoft, that it was developed by a small group of independent developers in some far off country that nobody ever heard of!
One thing about developing your own framework and making it a standard in the company is that it won't turn into a flavor-of-the-month entry. Goldman lead the way with OCEAN. Wachovia has OneSource, and Morgan Stanley has FidSharp and Concord. And we have ours. And, our companies tell our developers that they should use it.
No doubt that Acropolis will be "better" than CAB, and will have learned lessons and anti-patterns from CAB usage. Only, what will Microsoft come out with in another 6 months?
©2007 Marc Adler - All Rights Reserved
Subscribe to:
Posts (Atom)
