<HTML><HEAD></HEAD>
<BODY dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>Greetings,</DIV>
<DIV> </DIV>
<DIV>Fey?! Please, let’s not add more technologies (Haskell that compiles to
Javascript) in for geekiness sake. I have been reading this dialogue between
Robin and Kyle and thinking to myself, “Why was DBIC added in the first place?
Was it not to increase portability (where is that ‘it does not run on
Postgresql!’ person) , ‘simplify’ (at the cost of another learning curve) data
access, and provide a cleaner abstraction for data access?” So, why was it
added? Was it added to be more Object Oriented (OO) so we could use it in the
way that is being discussed? So, I’ll reiterate my question again, which I think
will bring some clarity to the discussion, what was the point of adding
DBIC?</DIV>
<DIV> </DIV>
<DIV>GPML,</DIV>
<DIV>Mark Tompsett</DIV>
<DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'></DIV></DIV>
<DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>P.S.
Abstractions are okay, but abstractions upon abstractions are ugly for the
initial learning curve. If you want people to join the coding community,
multiple levels of abstractions make it more
difficult.</DIV></DIV></DIV></DIV></BODY></HTML>