Should not we talk of the Djikstra hypothesis for computer environments instead of Sapir-Whorf? The tools we use have a profound (and devious!) influence on our thinking habits, and, therefore, on our thinking abilities. in this paper. What I like about Perl is that it takes malleability of the natural language without aping its surface syntaxe. Unlike Fortran and Cobol who are not malleable enough and take from natural language only a few words used as keywords.

Perl 6 is getting rid of the Perl 5 ossification to give a new meaning to malleability. Think Perl 6 macros for example. Introspection is proper to human thought, it should be the rules in programming languages. So the second Djikstra hypothesis, is wrong when you take it for its spirit : Projects promoting programming in "natural language" are intrinsically doomed to fail.

Speaking of syntax, the second language to impress me for its concision is Haskell, that I discovered thru pugs. Like Larry Wall did for Perl, the conceptors of haskell did put a lot of thought to get it right. It seens that most language designers don't think much about language syntax or for pedagogical reason stick to the convention of mainstream languages.

In the late eighties, Gosling, when designing NeWS, an innovating window system at the time, picked the postfixed syntax of PostScript with the clean semantic of the PostScript imaging system, dooming NeWS from the start. PostScript is intended to be generated by programs, not by programmers. Later, by mostly picking the C syntax, Gosling found a public for Java but, in my opinion, made it uninteresting from the start even if the idea of portability thru a virtual machine was brillant even if, in the long term, it did not panned out as well as expected. But this is due to refusing to make the language open source in due time, causing incompatible implementations and libraries.

-- stefp

In reply to languages and syntax by stefp
in thread What's wrong with Perl 6? by duff

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.