This is the funniest introduction to lambda-calculus ever. (saw it at #d channel . . . → Read More: Alligator Eggs!]]> Alligator Eggs!

This is the funniest introduction to lambda-calculus ever. (saw it at #d channel at freenode)

I mean:

This list can be continued more and more…

I perfectly understand the roots of current situation and I don’t ask to use . . . → Read More: Unicode vs. Programming Languages]]> I really-really want to see a programming language, which allows using proper unicode symbols for operators.

I mean:

• × instead of *
• → instead of ->
• ← instead if <-
• ≠ instrad of !=
• ≤ and ≥ instead of <= and >=

This list can be continued more and more…

I perfectly understand the roots of current situation and I don’t ask to use ONLY unicode-symbols, but I ask language-manufacturers to allow this.

It’s actually getting better now . . . → Read More: on documentation]]> People often debate on reasons of PHP’s success and “not so big success” of it’s more powerful competitors. My belief is, that one of the major parts of PHP’s win was it’s manual. All of the competitors had basic API documentation, but they didn’t have:

• syntax-highlighted examples for the majority of functions
• user-contributed comments

It’s actually getting better now (see documentation on Ruby’s CGI module, for example). But no-one is close enough.

One of the main concerns of the language core-team should be documentation. Better the docs are, more people will be comfortable to start using it for solving their problems.

If I have several weeks for digging into sources, I will probably chose the language which I like syntactically. But if the timeframe if small, I would definitely prefer the one which has better docs. Guess which situation tends to happen more often.

Something to think about:

• PHP Manual
• Python Manual
• Ruby Manual
• Haskell Manual
• Perl Manual

The good news is, that haskell software community started to adopt Trac for their needs too. One of the examples is MissingH library. The reason of “tracification” is simple: there is a stable darcs plugin available . . . → Read More: trac for haskell]]> Trac is one of the best things which happened to open-source software. But that is not news, really.

The good news is, that haskell software community started to adopt Trac for their needs too. One of the examples is MissingH library. The reason of “tracification” is simple: there is a stable darcs plugin available for trac

So, one more good article for the . . . → Read More: nice article about monads]]> Understanding of monads is an iterative process.. At one moment you think you understand them good enough, and the very next moment you know that everything you know is wrong.

So, one more good article for the next iteration

To . . . → Read More: “Hello world!” in Haskell]]> Everyone wants “hello world” application for being convinced, that the thing can work. Here is one written in Haskell and web-related. It’s quite straight-forward:

import Network.FastCGI
import Text.XHtml

htmlPage
  = header
    << thetitle
      << "Hello World!"
  +++ body ! [ bgcolor "white"] << "Hi"

main = runFastCGIorCGI (output (renderHtml htmlPage))

To make it working, you need GHC and fastcgi library (with all it’s dependencies)

Now, that I finally finished all the important stuff I will continue writing here. My main points of interest, for now, are: