IMO the real underlying problem is that as long as programmers expect to write a class and flip a switch to get a service or one or more RESTful resources then we have nothing really but RPC masquerading as something else. Both resource and service advocates would be well-off in trying to move the developer community to get past the “class is all I need” stage. If REST is successful in getting developers to get their hands dirty more power to it.
I say this all the time. I wish more people would listen to me!
People get caught up in automation and false simplicity. And then they are trapped, but it is too late. And then they go off searching for the next "simple" thing that will damn them. Odd really.
1 comment:
Geeks love elegance and one aspect of elegance is accomplishing as much as possible while simultaneously doing as little as possible. My high school math teacher, Miss Polly, called this "constructive laziness". Geeks are also comfortable with, and confident in, their intelligence. Between those two factors the idea that we could create a single class that solves all our problems becomes almost irresistable.
Post a Comment