Comments on: SOAP Destined to A Life of Obscurity http://blog.iandavis.com/2005/12/dare-obasanjo-aka-carnage4life-building-restful-applications-with-indigo blog.iandavis.com Wed, 04 Nov 2009 14:19:37 +0000 http://wordpress.org/?v=3.0-alpha hourly 1 By: John McDowall http://blog.iandavis.com/2005/12/dare-obasanjo-aka-carnage4life-building-restful-applications-with-indigo/comment-page-1#comment-268 John McDowall Sat, 17 Dec 2005 05:40:02 +0000 http://iandavis.com/blog2/?p=909#comment-268 While I have not looked at Indigo I can say that .Net 1.1 is REST hostile and makes doing simple things extremely hard, while Java Servlets makes it trivial to enable the creation of a REST interface. .Net tries to make development wizard driven and hide the complexity and in doing so puts a straight jacket on the developer which constrains the style they choose to develop in. Java, Perl, Python, Ruby, etc are much more open ( and hence require more knowledge) so can be adapted to any design pattern easily if you have the skill and knowledge. In essence the Indigo/.Net approach is to tell developers to pay no attention to the man behind the curtain or just trust us. If the architectural patterns are well defined this may work but we are still defining the path to teh best approach to a services based network and these constraints just get in the way. While I have not looked at Indigo I can say that .Net 1.1 is REST hostile and makes doing simple things extremely hard, while Java Servlets makes it trivial to enable the creation of a REST interface. .Net tries to make development wizard driven and hide the complexity and in doing so puts a straight jacket on the developer which constrains the style they choose to develop in. Java, Perl, Python, Ruby, etc are much more open ( and hence require more knowledge) so can be adapted to any design pattern easily if you have the skill and knowledge.

In essence the Indigo/.Net approach is to tell developers to pay no attention to the man behind the curtain or just trust us. If the architectural patterns are well defined this may work but we are still defining the path to teh best approach to a services based network and these constraints just get in the way.

]]>