|
PureBytes Links
Trading Reference Links
|
Well based on that criteria and everyone's individual viewpoint, there
would be no Windows or Dos of any kind. Which puts you back at card
punching your program into a large costly main frame that is being shared
by many people. We could also extrapolate that definition to cars,
houses, spouses, etc. etc. What many on this thread forget is that when TS
was introduced it was like a godsend for traders, they could sit in their
offices or homes and it was virtually like being on the floor. It was, and
is, a competitive, quantum leap if you will, over the floor brokers and the
big time PRO traders; It gave the little guy the "ability" (not the
guarantee) to compete and beat the market on a REALTIME basis. You have
the ability to input your very own, individual ideas, such as they may be,
and try them out, (and believe me I have spent hours programming some real
stinkers) another quantum leap. (assuming you had the correct idea for the
holy grail or as I call it the "secrets of the universe"). I believe that
most of the bitching comes from those of us that are the most impatient,
and that is a good thing in general. I remember that I talked to Omega
about the ability to split a symbol back in 91 or 92 (I trade stocks) and
nothing happened until the xmi split then lo and behold it was a done deal.
It used to be that if I wanted to build a new chart and put my favorite
indicators, systems etc. on it it could take up to 10 or 20 minutes; now it
is one mouse click away!
No nothing ever happens as fast as any of us would like but it is a hell
of a lot better than going back to carbon paper. My point is, this is a
good solid product that (at least for me) more than pays for itself many
many many times over every year and I don't know how many products of any
kind that I have used over my lifetime that I could say that about.
----------
> From: Carroll Slemaker <cslemaker1@xxxxxxxx>
> To: omega-list@xxxxxxxxxx
> Subject: Omega Research - Saviour or Demon?
> Date: Friday, January 16, 1998 4:13 PM
>
> Many posts have appeared damning Omega and others defending Omega.
> Many of those, unfortunately, have been mainly emotional and not
> well thought out. Some defenders, for example, have said, in effect,
> "If you don't like TS, then quit using it!" This reveals a gross
> insensitivity and a lack of grasp of the issues involved. If a person
> has paid one or two thousand dollars for a product, it's not easy to
> simply scrap it and chalk the experience up to bad luck.
>
> Therefore, I'd like to offer the following as an ethical foundation
> for discussions of this subject, a list of what a customer should
> fairly expect from a software creator/vendor. But note carefully the
> opening clause which begins "Unless . . ." So here goes:
>
> UNLESS the customer is provided by the vendor BEFORE the sale with a
> written statement or specification which CLEARLY describes all
> exceptions to the following, a customer has a right to expect the
> following, and the vendor has an ethical (if not a legal) obligation
> to provide the following:
>
> 1. Software which is robust. "Robust", with respect to software,
> means that it behaves gracefully "under fire" - it traps and handles
> in an appropriate manner all user-input and data errors; it never
> responds to such conditions in an uncontrolled manner by aborting,
> crashing the system, or corrupting itself or its data, especially
> where the corruption is covert - not immediately apparent. The
> engineering rule for robust software is that any secondary damage
> caused by user or data error must be controlled and kept to an
> absolute minimum.
>
> 2. Product defects which are encountered by customers will be
> promptly corrected by the vendor, or a workaround will be devised,
> or the customer will be offered the option of a refund of the
> purchase price. What is a defect? A defect is any operation which
> is contrary to what is described in the documentation. And if the
> documentation is ambiguous or incomplete, then the standard will be
> however the average reasonable customer would expect the software
> to operate based upon the available documentation AND advertising
> materials and operational characteristics of other similar products.
>
> 3. The vendor will maintain a list of reported defects/problems
> in which symptoms and workarounds, if any, are clearly and
> completely described. This will permit some customers to avoid
> the problem with its attending frustration and loss of time (and,
> perhaps, money).
>
> 4. If the documentation is ambiguous, unclear, or incomplete, then
> a convenient, accurate, and effective technical-support program
> will be provided by the vendor.
>
> ***********************************
>
> There it is. What do you think? Does Omega meet this standard?
>
> Carroll Slemaker
>
|