This post originated from an RSS feed registered with Agile Buzz
by James Robertson.
Original Post: necho thoughts (again)
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
nEcho continues to fly off the rails. I'm afraid this process is broken; perhaps, irreparably. (Roger Benningfield, Doug Miller, Zeldman) In the absence of any sort of agreement on the desirability of junking XML-RPC, it seems that people decided to 'declare consensus'.
This sure ain't the consensus I learned about at a Quaker college.
The upshot of requiring every server to support three separate interfaces will be to ensure that none of the interfaces will actually be definitive. This leads, in turn, to the standard being "whatever works". People will write software to cater to bugs. People will write clients for programs, not standards
Yeah, I'm in agreement again. Maybe all of us necho cynics should get together and drown our sorrows.... It is hard to keep up with the laundry list of API's being churned. Trackback and Pingback (at least 3 different forms, by my last count - and from the outside, how the heck do you tell which one an advertised link uses? Then there's going to be an necho variant, I'm sure. The Blogger API, and the MetaWebLog API's, and the necho variants (using gosh only knows how many forms - REST, SOAP, but not XML-RPC).... The level of complexity is growing by the minute.
Previous Topic
