Comments on: An Open Letter to Scott Guthrie http://elegantcode.com/2007/03/22/an-open-letter-to-scott-guthrie/?utm_source=rss&utm_medium=rss&utm_campaign=an-open-letter-to-scott-guthrie Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Yurtd??? E?itim http://elegantcode.com/2007/03/22/an-open-letter-to-scott-guthrie/comment-page-7/#comment-63824 Yurtd??? E?itim Mon, 09 May 2011 18:28:00 +0000 http://elegantcode.com/?p=539#comment-63824 Excellent letter! Having used monorail I must say it is a great clean elegant design. If microsoft does it right it would truly rock.... thank's... Excellent letter! Having used monorail I must say it is a great clean elegant design. If microsoft does it right it would truly rock…. thank’s…

]]> By: Soma. http://elegantcode.com/2007/03/22/an-open-letter-to-scott-guthrie/comment-page-7/#comment-36929 Soma. Sun, 09 Nov 2008 11:47:53 +0000 http://elegantcode.com/?p=539#comment-36929 <strong>Soma....</strong> Drug soma.... Soma….

Drug soma….

]]> By: Prozac. http://elegantcode.com/2007/03/22/an-open-letter-to-scott-guthrie/comment-page-7/#comment-36808 Prozac. Thu, 06 Nov 2008 18:55:46 +0000 http://elegantcode.com/?p=539#comment-36808 <strong>Prozac....</strong> Phentermine prozac. Prozac mood disorder. Prozac side effects. Prozac misuse. Phentermine and prozac. Prozac.... Prozac….

Phentermine prozac. Prozac mood disorder. Prozac side effects. Prozac misuse. Phentermine and prozac. Prozac….

]]> By: Deepak http://elegantcode.com/2007/03/22/an-open-letter-to-scott-guthrie/comment-page-7/#comment-29668 Deepak Wed, 13 Aug 2008 12:12:09 +0000 http://elegantcode.com/?p=539#comment-29668 David, You may want to moderate comments on your blog. Comments from Paris Hilton about her attributes isn't very impressive :) David,

You may want to moderate comments on your blog. Comments from Paris Hilton about her attributes isn’t very impressive :)

]]> By: Deepak http://elegantcode.com/2007/03/22/an-open-letter-to-scott-guthrie/comment-page-7/#comment-29667 Deepak Wed, 13 Aug 2008 12:10:30 +0000 http://elegantcode.com/?p=539#comment-29667 I am impressed that Scott Guthrie posted a comment on this post. Now my opinion: I think lately Microsoft has been sending some very mixed signals about the direction of their efforts. For example consider LINQ To SQL and Entity Framework. Obviously one is better than the other and both are part of the framework. So why have something which is inferior? I can understand if it was done to maintain backward compatibility but with LINQ To SQL, what backward compatibility? No one has produced anything other than tutorials on how to use it. I am impressed that Scott Guthrie posted a comment on this post.

Now my opinion:

I think lately Microsoft has been sending some very mixed signals about the direction of their efforts. For example consider LINQ To SQL and Entity Framework. Obviously one is better than the other and both are part of the framework. So why have something which is inferior? I can understand if it was done to maintain backward compatibility but with LINQ To SQL, what backward compatibility? No one has produced anything other than tutorials on how to use it.

]]> By: Ritalin shipping. http://elegantcode.com/2007/03/22/an-open-letter-to-scott-guthrie/comment-page-7/#comment-26024 Ritalin shipping. Mon, 07 Jul 2008 01:19:04 +0000 http://elegantcode.com/?p=539#comment-26024 <strong>Ritalin shipping....</strong> Ritalin shipping.... Ritalin shipping….

Ritalin shipping….

]]> By: Paris hilton no underwear. http://elegantcode.com/2007/03/22/an-open-letter-to-scott-guthrie/comment-page-7/#comment-23882 Paris hilton no underwear. Sun, 15 Jun 2008 04:51:58 +0000 http://elegantcode.com/?p=539#comment-23882 <strong>Britney spears paris hilton photos....</strong> Paris hilton nude.... Britney spears paris hilton photos….

Paris hilton nude….

]]> By: Good http://elegantcode.com/2007/03/22/an-open-letter-to-scott-guthrie/comment-page-7/#comment-19827 Good Wed, 16 Apr 2008 14:23:49 +0000 http://elegantcode.com/?p=539#comment-19827 http://Good.com http://Good.com

]]> By: Thomas Hansen http://elegantcode.com/2007/03/22/an-open-letter-to-scott-guthrie/comment-page-6/#comment-17789 Thomas Hansen Sun, 17 Feb 2008 20:14:21 +0000 http://elegantcode.com/?p=539#comment-17789 Oh yeah, I almost forgot... "And our HTML5 video tag wrapper Ajax Widget and our HTML5 canvas tag wrapper Ajax Widget"... Good luck MSFT, you'll need it! :D Oh yeah, I almost forgot…
“And our HTML5 video tag wrapper Ajax Widget and our HTML5 canvas tag wrapper Ajax Widget”…
Good luck MSFT, you’ll need it! :D

]]> By: Thomas Hansen http://elegantcode.com/2007/03/22/an-open-letter-to-scott-guthrie/comment-page-6/#comment-17788 Thomas Hansen Sun, 17 Feb 2008 20:10:41 +0000 http://elegantcode.com/?p=539#comment-17788 The only way to ensure MSFT won't steal your baby is to make sure you're going down a path they cannot possible follow you. Like for instance have 100% Mono support, branches to make it run through GrassHopper or create some piece of SW library that if successful would kill large parts of their revenue... (Like we've done ;) Let's take an example: I know Charlie Poole and I have encouraged him to get nUnit ported 100% to Mono simply because MSFT would never be able to "outperform" that feature. Another great feature for nUnit would be to integrate even better than what it does today with other tools like for instance Boo, nAnt etc... A tool is never better than the sum of tools it is compatible with... If for instance Cruise Control, nAnt, nUnit and nCover would be 100% compatible with Mono with a common IDE which could be installed from the same exe file on both Linux (through Mono) and Windows MSFT would never be preferred and they would not be able to follow... Another point to outperform MSFT so that they'll never follow you is to focus on standards. An example would be if all the ORM library vendors for .Net would agree on a common standard for marking classes as serializable so that users could easily change between one ORM library vendor to another which effectively would foster competition and make MSFT stand alone in their proprietary version of serializable support etc. Imagine a common standardized version of HQL or .hbm format files, THAT would be awesome ;) Look at their Ajax library for instance, MSFT have never been able to compete in an open and standardized world. Even Michael Schwarz and Jason Diamond being *ALONE* outperformed those guys by a gazillion. Why; because MSFT don't know how to compete when something is open and standardized. Not to mention if Ajax prevails they loose about 66% of their revenue. If MonoRails would standardize and maybe collaborate with other SW library vendors to create something 100% compatible with Mono and with a common interoperability way to describe stuff they would prevail. Period. Imagine how super cool it would be to have MonoRail run on J2EE through GrassHopper! Or maybe their Java counterpart having the exact same class hierarchy and API! Or simply creating an MVC implementation that would be compatible with *WebControls*...? (And thereby having a "gazillion" WebControl vendors building value on top of their own product) Until they *do* they don't really stand a chance of becoming something better then MSFT's "research department"... (And I am not really sure if they deserve it either) Now returning to implement my GrassHopper and IKVN port of Gaia ;) (We've got Mono already :D The only way to ensure MSFT won’t steal your baby is to make sure you’re going down a path they cannot possible follow you. Like for instance have 100% Mono support, branches to make it run through GrassHopper or create some piece of SW library that if successful would kill large parts of their revenue…
(Like we’ve done ;)
Let’s take an example:
I know Charlie Poole and I have encouraged him to get nUnit ported 100% to Mono simply because MSFT would never be able to “outperform” that feature. Another great feature for nUnit would be to integrate even better than what it does today with other tools like for instance Boo, nAnt etc…
A tool is never better than the sum of tools it is compatible with…
If for instance Cruise Control, nAnt, nUnit and nCover would be 100% compatible with Mono with a common IDE which could be installed from the same exe file on both Linux (through Mono) and Windows MSFT would never be preferred and they would not be able to follow…
Another point to outperform MSFT so that they’ll never follow you is to focus on standards. An example would be if all the ORM library vendors for .Net would agree on a common standard for marking classes as serializable so that users could easily change between one ORM library vendor to another which effectively would foster competition and make MSFT stand alone in their proprietary version of serializable support etc. Imagine a common standardized version of HQL or .hbm format files, THAT would be awesome ;)
Look at their Ajax library for instance, MSFT have never been able to compete in an open and standardized world. Even Michael Schwarz and Jason Diamond being *ALONE* outperformed those guys by a gazillion. Why; because MSFT don’t know how to compete when something is open and standardized. Not to mention if Ajax prevails they loose about 66% of their revenue. If MonoRails would standardize and maybe collaborate with other SW library vendors to create something 100% compatible with Mono and with a common interoperability way to describe stuff they would prevail. Period. Imagine how super cool it would be to have MonoRail run on J2EE through GrassHopper! Or maybe their Java counterpart having the exact same class hierarchy and API! Or simply creating an MVC implementation that would be compatible with *WebControls*…?
(And thereby having a “gazillion” WebControl vendors building value on top of their own product)
Until they *do* they don’t really stand a chance of becoming something better then MSFT’s “research department”…
(And I am not really sure if they deserve it either)
Now returning to implement my GrassHopper and IKVN port of Gaia ;)
(We’ve got Mono already :D

]]>