<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Alberto,<br>
<br>
you are working on *second order scalibility*?? Great. May I regard you
a one of the first of a breed of Haskell business evangelists?? ;-)) <br>
<br>
Somebody stated here - sorry, the name's missing - the relevance of
Hackage being diminuished by the great amount of *scientific*
libraries, no joke... Personally, I don't think Haskell should become
like Java & Co. So for at least for two reasons, I see at least two
reasons to speak open about what you are seemingly interested:<br>
<br>
o to support Haskell library developers to better realize the value
of their work, and teams intending software projects in the
non-standard areas to realize advantages of using Haskell, once they
are given<br>
<br>
o to prevent conflicts, when Haskell grows economically more
successful, and allowing a harmonious transition between both cultures<br>
<br>
Keep on the work ;-)<br>
<br>
Nick<br>
<br>
Alberto G. Corona wrote:
<blockquote
cite="mid:a13b39160909301239i5afc001ak2a5d74bc62cc46a1@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000">
<div class="im">
<blockquote type="cite">
<div>
<div><br>
</div>
</div>
</blockquote>
</div>
This reminds me of the whole agent thing -- pretty much dominated by
Java (e.g., Jade, Jason, Jack) nowadays --, for which I would bet lots
things are done more straigthforward using Haskell -- especially those
parts the Java coders are usually proud of... Let's maybe speak of
*second order scalability*: <br>
<br>
As first order scalability would rather be a matter in space time load
increased by repetitions, the concern of second order scalability would
be more about a *fractal* expansion of concepts like a *closure* --
Haskell, already in a vivid exchange with interactive theorem proving
(e.g. Coq adopts type classes from Haskell and dependent types vice
versa) seems excellently prepared... :-)<br>
</div>
</blockquote>
<div><br>
</div>
<div>Interesting. I´m working in something like second order
scalability. Instead of brute performance by redundancy, high speed
networks and fast disks, scalability can be achieved by looking at the
properties of the data. </div>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"><br>
I ever tended to say financial applications are especially prone to be
boring -- the prototype of repetitive IT, even for strategy the stupid
'traffic lights cockpits' or OLAP(!) ... But this problem is rather
supply driven to me.<br>
<br>
</div>
</blockquote>
<div>For sure. This is supply driven. There are a lack of new ideas
mainly because the technology is low level and obsolete.</div>
<div> </div>
</div>
</blockquote>
<br>
</body>
</html>