skaller wrote:
> I'm hopefully off to a job interview soon for a SCADA
> application (industrial automation). C++/C# combo on Windows.

I'm so sorry :)

> There are SO many applications for Felix. All my current
> efforts have been on the compiler and type system.
>
> But the primary market is for the multi-threading model:
> that's the key feature that distinguishes it from other
> languages: it's easier to point to a performance graph
> and show some nice simple fibrated code than explain
> the advantages of advanced type systems.
>
> I barely understand what a GADT is .. how would I 
> explain how it helps a commercial client?

I'm off to lunch so this will be quick, but I don't think you can, or 
would really want to at first. To be honest, I don't understand them 
either :) One of the things that has turned me off haskell many times 
was that I just didn't understand a lot of the language that is used in 
it's documentation. Things like monads, comonads, _|_ (bottom), and etc 
are a lot to comprehend. ocaml's docs were a bit nicer about hiding the 
theory. For documentation, if we can't come up with a simple 
description, then it should be put in the "advanced" section.

Maybe some documents like this?

http://www.ffconsultancy.com/languages/ray_tracer/index.html

Where we compare one set of code written in c++/java, and another 
written in felix that's easy to understand without getting too deep into 
theory? I'm a much bigger fan of allowing people to slowly learn the 
more advanced features.

-e

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Felix-language mailing list
Felix-language@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/felix-language

Reply via email to