Re: Pick query languages compared to SQL
- From: "Glen B" <no$pamwebmaster@no$pamforallspec.com>
- Date: Thu, 9 Mar 2006 12:56:52 -0500
"Simon Verona" <nomail@xxxxxxxxxx> wrote in message
news:440fc943$0$70286$ed2619ec@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Been watching this thread sitting on the fence...
The MV query system (AQL/jQL/English/Access) and the dictionaries relating
to it are just to "1970's" thse days.. I'm not saying I prefer SQL, but
SQL has had solid development over the past 20 years whereas largely MV
has stood still...
Think about why that is. Who drives this market? Who drives the relational
market? If you really analyze things, you'll come to the conclusion that
end-users drive this market. That's not a good thing! The developers drive
the relational market, which is why their market (and subsequently their
customer base) is far more advanced. Why the difference? It comes down to
product stability, evolution, and maturity. When a product reaches maturity,
it rarely changes. Why mess up a good thing? Somtimes you need to mess up a
good thing. in order to keep up with the times. People here don't like those
risks. In the case of MV applications, the applications mature with the DB
as long as the customers buying the product agree with the maturity level.
If you don't present new technology to the customer base, then the customer
base has no idea that the new technology exists and how it can save them
money, time, or a combination of both. Also, how that technology is
presented determines how the technology will be received and perceived.
Developers, as a collective, drive IT markets regardless of where the real
influence appears to be. The VARs and application vendors determine how
technology is sold and marketed. There seems to be a trend of obtuse
development to achieve too many goals. Technology marketing isn't about how
many solutions you can solve with your uber product. It's about presenting a
simple method to a solution, in terms that the buyer totally grasps. We
still don't get that here! We either have a product that's overkill and over
priced, or it's under priced and obscure. That is why CSV isn't an old
technology in the MV databases. We've taken the core design steps from the
vendors and assumed it as our own, poorly profitable, responsibility. Hey,
the vendors won't complain! It's less R&D, development, and testing. They'll
sit around and watch until enough developers say, "Hey.. this is pointless.
We're all competeing against each other with tools that every DB should
support natively!" Finally, a global light bulb will click and masses will
start complaining about it. By then, 5-10 years have passed and it's now too
late to "get on-board" with the rest of the world. Everyone has spent that
huge amount of time taking profit from one-another, when we all(DB vendors,
VARs, and developers) should have been taking it from other markets.
[chop]
Regards
Simon
Glen
.
- References:
- Pick query languages compared to SQL
- From: dawn
- Re: Pick query languages compared to SQL
- From: Tom deL
- Re: Pick query languages compared to SQL
- From: dawn
- Re: Pick query languages compared to SQL
- From: Kevin Powick
- Re: Pick query languages compared to SQL
- From: Glen B
- Re: Pick query languages compared to SQL
- From: Kevin Powick
- Re: Pick query languages compared to SQL
- From: Simon Verona
- Pick query languages compared to SQL
- Prev by Date: Is free software good for developers?
- Next by Date: Re: Howto MVbase phantom
- Previous by thread: Re: Pick query languages compared to SQL
- Next by thread: Re: Pick query languages compared to SQL
- Index(es):
Relevant Pages
|