4 ms·
Haskell (and Lisp) will always be 'new'. Especially going by HN posts which seem to think that Haskell is some brand new language created last week to solve the
by RyanZAG 13y ago
Haskell (and Lisp) will always be 'new'. Especially going by HN posts which seem to think that Haskell is some brand new language created last week to solve the problem of 'side effects' and in a few months time everyone will be using it.
- pjmlp 13y agoI have spent part of the holidays reading about Interlisp and Mesa/Cedar systems at Xerox PARC. Quite powerful GUI desktop systems in the early 80s, using language capabilities that are yet to be fully usable in the mainstream. Lisp on one system, and a GC enabled systems programming language on the other one. Every time I discovered such systems being ignored most developers, I remember of Bret Victor's talks.
- IsTom 13y agoDon't forget Erlang. For some reason a big part of HN thinks it's an unproven technology.
- nknighthb 13y agoI don't know of anyone who thinks Erlang is unproven. Lots of us think it's weird and not worth using.
- pjmlp 13y agoYet, your mobile phone calls might be going through Erlang powered switches.
- throwaway2048 13y agoAnd my multi kilobuck bank transactions may be powered by COBOL, but you won't see very many developers lining up for that.
- nknighthb 13y agoBuilt by a company with the time, money, and motivation to train new hires on an esoteric language that happens to be specifically designed for their unique application. (Incidentally, my mobile phone calls are quite rare. Voice communication sucks. If your intent was to show that Erlang is important to me, you chose a poor example.)