| Like you bill there are many things/areas where I believe ease of use could
really use a boost, though I temper that with the belief that if it is
easy to use but doesn't do enough we are back to peg one.
Keeping that in mind I believe we need to make it easier for people to
write their own xM's/specials that integrate with DECmss. Things like
being able to plug in existing applications so that they can be used from
DECmcc, or even building a new xM using DCL or shell scripts so that
managers/support personnel can enhance their own environments. To this
end we have seen quite a bit of xM work going on in house (even some
announced in this conference like the stock AM and the ping AM), what better
way to encourage xM development but to make some of these things available
through the DECUS library? Keep in mind this is my opinion....
Ease of use starts with ease of development. The easier it is for me to add in
the functions I am really looking for, then the more apt I am to feel that
it meets my needs.
jill
|
| re: .-1:
Jill,
Ease of use should not be confused with ease of development. I work in
DECnet-ULTRIX, UNIX is a very attractive development environment which
is devilishly hard to use, and with DNU NCL I have received many
compliments on ease of plugging in new entities to it but that in no
way improves the ease of use for customers, who were stunned by how
difficult EFT NCL was to understand, let alone use. Since then, several
features such as command line recall and better online help have been
put in place to try to improve ease of use, but none of these features
had anything to do with ease of development.
Ease of development is not even a necessary condition for ease of use.
It's possible to write a total hack program that is extremely easy to
use but is unextensible and non-maintainable, it's called a demo.
Sorry to have to disagree, but this is a very fundamental point.
ben
|