Comments on: Developers Reaping What They Sow? http://www.dancres.org/blitzblog/2007/07/12/developers-reaping-what-they-sow/ Sat, 05 Jul 2008 08:38:47 +0000 http://wordpress.org/?v=2.3.3 By: Dave Zaffery http://www.dancres.org/blitzblog/2007/07/12/developers-reaping-what-they-sow/#comment-712 Dave Zaffery Fri, 13 Jul 2007 14:27:09 +0000 http://www.dancres.org/blitzblog/2007/07/12/developers-reaping-what-they-sow/#comment-712 Sounds like a similiar tune that the old J2EE spec designers used, thus the containers were born... On one hand I understand having the layers to manage the network details, but by the same token developers sometimes need to be able to modify things to suit the needs of the application they are building. I believe that is one of the reasons that frameworks like Spring were born, they allow the best of both worlds, using only as much or little as your truly need. Sounds like a similiar tune that the old J2EE spec designers used, thus the containers were born… On one hand I understand having the layers to manage the network details, but by the same token developers sometimes need to be able to modify things to suit the needs of the application they are building. I believe that is one of the reasons that frameworks like Spring were born, they allow the best of both worlds, using only as much or little as your truly need.

]]> By: Udi Dahan http://www.dancres.org/blitzblog/2007/07/12/developers-reaping-what-they-sow/#comment-711 Udi Dahan Fri, 13 Jul 2007 07:09:45 +0000 http://www.dancres.org/blitzblog/2007/07/12/developers-reaping-what-they-sow/#comment-711 While I do agree that separation of concerns is important, and the ability to write business logic that is independent of network protocols provides value, that is no reason for developers to entirely ignore those other concerns. Conversely, the WS-* point of view seems a bit high-and-mighty. To believe that they know more about everyone's specific domain is inconceivable. That, however, is the problem of all general purpose things - 80/20 and all that. Regardless of WS, REST, or anything else, developers "placing their fate in others hands and paying the price" will continue to happen. While I do agree that separation of concerns is important, and the ability to write business logic that is independent of network protocols provides value, that is no reason for developers to entirely ignore those other concerns.

Conversely, the WS-* point of view seems a bit high-and-mighty. To believe that they know more about everyone’s specific domain is inconceivable. That, however, is the problem of all general purpose things - 80/20 and all that.

Regardless of WS, REST, or anything else, developers “placing their fate in others hands and paying the price” will continue to happen.

]]>