I've always thought that there was a difference of philosophy from Day 1
that underlied the 2 organizations that manifests itself in the
software:
Vmark/UV: "All things to all men, that I might by all means sell to
some."
(If you'll allow me to misquote St. Paul.)
UniData: "Do it right."
They took the opportunity to recreate MV & PI "in their
own image." (I'm continuing to bastardize the Bible.)
There are pluses & minuses to each approach. I am NOT arguing which is
better, just that some differences in the products can be explained in
terms of the respective philosophies of the organizations.
Examples:
1. Conversions from other MVs:
UV: inherently easier. Baskin&Robbins 31 Flavours.
UD: supplies conversion tools to help you, since it is more extensive.
2. UV tends to resolve ambiguities and go on, where UD tends to abort.
That means you might get up and running with UV sooner, but UD aborts on
bugs that need to be resolved.
That can be characterized in terms of rigidity/flexibility. Those EACH
have positive AND negative connotations, with respect to Software
Quality Attributes, both inherent within UV & UD itself, and in your
ability to build quality into your ap using each environment.
Consider the implications on:
Correctness Dependability Learnability
Efficiency Portability Robustness
What is important to you would influence your preference of UV or UD.
By the way, I've worked in UV much more than UD, which is fine by me.
But take that as circumstance of history, more than personal bias.
Chuck Stevenson
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
