'' Currently, the most common way to bring data from databases
into an application developed in .Net is through SQL (structured
query language). However, SQL uses a completely different vocabulary
from languages such as C# and VB that .Net developers use to build
applications, so it takes a lot of coding to bring the two languages
together in one development framework
Programmers writing
enterprise applications [say] that sometimes when it comes to data,
they feel more like plumbers than programmers because they have
to create ways to link the two languages to access data. There is
no native understanding of the query language in C# or Visual Basic.
''
So despite the OOP sales pitch about improving developer productivity,
the two worlds of OOP and RDBMs do not fit at all well together.
OOP, by its very nature, consists of small bits of code inextricably
wedded to small bits of data. The relational database model on
the other hand is totally divorced from code. The conjugal gymnastics
required to mate this unlikely couple can easily generate 40%
extra effort - in return for little to no incremental value.
Genero embeds SQL directly into the language. That's what you
would expect from a language designed for business applications.
|