Re: RDBMS for DOS and Windows

new topic     » goto parent     » topic index » view thread      » older message » newer message

Having several customers that fit this description, I can tell you that
misinformation or outmoded information is more likely the culprit than
lack of money. Many of the these old "penny pinchers" (and how do you
think most of them got wealthy in the first place) paid two to four
thousand dollars per machine for their original networks plus more for
networking software and even more for custom accounting software...many
times up into the hundreds of thousands of dollars for even fairly small
setups. Their expectations for the replacement are more of the same. When
presented with a proposal for client machines at well under 1k per pop
and servers for anywhere from $1000 to 10k or more depending on number of
clients, they are usually delighted to move into the modern world, no
matter how "tight" they are. Especially when they see the amount of
off the shelf software now available that can be trimmed up to their needs
with minimal stirring. People time is the most expensive item around and
highly optimized code on tiny processors may be wonderful for a Mars
mission where such parsimony is enforced by the requirements...but then
you see what happens to a lot of Mars missions. A lot of very expensive
person hours can be traded in for a faster cpu, more RAM and disk and
faster communication. Real slop is inexcusable, but building block code
is highly efficient from a Return on Investment viewpoint. Even
interpreters and compile and go systems can be justified in such systems:)
which leads us back to where we are. We need to be able to easily wrap
all the building blocks out there with this superbly "person efficient"
coding engine that we all love to "play" with. Easy access to all these
items through structures that can easily describe all those interfaces
tethered together with namespace improvements to allow more easy
modularity of use of external code, along with more flexible and
powerful calling conventions enabled by items one and two can make
Euphoria into a premiere integrator language on that new, faster, cheaper
hardware. Then we can go to the old skinflint and say, I'm going to
make you money by leveraging all this inexpensive hardware and software
in to an integrated whole that serves your specific needs.

Everett L.(Rett) Williams
rett at gvtc.com

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu