Five years from now, the concept of an application will be obsolete […] They will all be services, combined, mixed, matched and reused as needed.As you can see from the two papers I authored at each of the OOPSLA ’96 and OOPSLA ’97 Business Object Workshops, in particular the latter one, I had similar thoughts;
Distributed objects, specifically business objects, are not about building a better application. They are about replacing the application as the predominant means of delivering value to customers.The first paper also gets at this, though indirectly through workflow-coloured glasses;
Work items and lists are outdated. In the world of business objects, the desktop is the interface. As Oliver Sims preaches, OO document centric GUIs are how business objects will present themselves to their users. And they won’t be shy. They won’t disguise themselves because there is no need to. Users will recognize them as entities in their business domain, and they’ll understand (in most cases, intuitively) what it means to do typical OO GUI operations on them. Icons representing the business objects themselves will clutter the screen. Nebulous ‘work item’ concepts don’t fit customer relationships management. They aren’t objects. Work is a consequence of what happens when business objects play together on desktop GUIs as directed by users.Boy, that’s some awkward writing though. Ouch. That first one, from ’96, was the first paper I ever submitted anywhere. I remember that I wrote it in a couple of hours, right after a discussion with my friend Chester Kwok where he helped me finally “get” objects. It’s funny, looking back, to see how close I was to understanding the Web at that point, and how “getting OO” was so closely related to the “getting” of REST. Why didn’t I associate “typical OO GUI” operations with GET (double-click/open), PUT (save), POST (the ‘drop’ of ‘drag-and-drop’), DELETE (drop-to-garbage-can) then? Grrr… Compare and contrast this too;
Therefore, not only are business objects built from a framework, they can (and should, if they’re competing to be reused) also be frameworks.
Gee, tell me something I don’t know!
Sorry, Paul, I too get the “a very well-developed sense of Right and Wrong and believe in economic fairness” descriptor.
| You are a Social Liberal (83% permissive) and an… Economic Conservative (65% permissive) You are best described as a: Libertarian
Link: The Politics Test on OkCupid Free Online Dating Also: The OkCupid Dating Persona Test |
In a comment on a pro-REST, anti-SOA post, this gem;
REST has the potential to transform and simplify data exchange using many of the same idioms that have been maturing with the Web for 11 years. In my opinion, SOAP has the potential to…keep us shackled to outdated architectural ideas.
8-)
My wife got a Blackberry from work a few weeks ago, so, no longer needing her existing mobile phone, I called our carrier, Rogers to cancel it, which was handled promptly and without comment by Rogers, except to ask why we were leaving (expected, of course). Fast forward to last Friday, when I receive a bill with a surprise C$200 charge due to “Early contract termination”. Ouch!
First thing this morning, I’m on the phone to them. As I’m waiting for a service rep, I’m contemplating various plans of attack for what will surely be an awkward-at-best conversation. The rep picks up a minute or two later, asks about the problem to which I provide a brief synopsis of the situation. I did sign a contract, which had almost another year left, but when I informed her that nobody mentioned a cancellation charge at the time I cancelled – and without skipping a beat – she responds “I apologize Mr. Baker – we’ll refund that right away”!
Gosh, that was unexpected, but very welcome. Thanks, Rogers.
