• littleomid ( littleomid@feddit.org ) 
    link
    fedilink
    English
    arrow-up
    21
    ·
    edit-2
    2 months ago

    I will never not post this picture on this subject. Skimmed through the article, seems well written and will read it later.

    Edit: did read it through, and don’t necessarily agree. I don’t think about any of this when writing lisp code. Emacs deals with my parens, as does paredit and structural editing. This discussion ignores the things that makes lisp work: s-expressions. By changing this main feature, one destroys lisps best feature.

  • Feyd ( Feyd@programming.dev ) deleted by creator
    link
    fedilink
    arrow-up
    8
    ·
    2 months ago

    It’s honestly more familiarity than anything else, and it’s mostly that Polish notation isn’t how people learn to read math in school. If Polish notation was how math was notated then lisp would be the easy one to pick up. Similar to how natural languages have the parts of speech in different places in sentences.

  • Azzu ( Azzu@leminal.space ) 
    link
    fedilink
    arrow-up
    6
    ·
    2 months ago

    I agree very much.

    When I started developing in Clojure, I came across a lot of Clojure code that simply seems to be formatted/aligned “wrongly”, which was just my intuitive understanding of what the article names more accurately.

    It felt to me like everything was too cramped, not grouped properly.

    Luckily, it was super easy to fix for me in my code, just do some different alignment and line breaks and readability increased a lot. However, it now doesn’t look like “standard Clojure” which might be its own problem in collaboration, I don’t know.

  • I’m still convince that polish notation was the biggest mistakes of Lisp. At some point, the guy who create Lisp language decide to get rid of 2 centuries of mathematic convention just because of a technical limitation that last for maybe 2 decades.

    Oh, and no one to talked about (1- x) ?

  • I get because I was like that when I first experienced lisp but I like lisp now.

    I found it pretty messy when I was going through the land of lisp book but lisp is pretty flexible and you can make it readable.

    When I was converting my 3d game engine to hare lang I missing the flexibility of lisp.

  • Denys Nykula ( nykula@piefed.social ) 
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 months ago

    JS written by different people became easier to read since Prettier appeared. When others’ code is formatted just like your code, it saves effort. Idk if Scheme or other Lisps have standard formatters now; there wasn’t one for Guile when I learned it.

      • Why should LISP always be formatted in a way that’s unreadable? That can’t that be the defining property of LISP, can it?

        Haskell unfortunately has literature which doesn’t read well to me. All examples are jumbles of letters f(a, b, c) with “as one can clearly see”. It’s as if I’m reading a math textbook. It’s like nobody writing a Haskell book is an actual educator. Python’s documentation is a better intro to the language than any Haskell book I’ve read.

        Never heard of rhombus, but I’ll check it out, thanks.

        • littleomid ( littleomid@feddit.org ) 
          link
          fedilink
          English
          arrow-up
          4
          ·
          2 months ago

          Because if you don’t write it this way, then it’s not lisp. I would recommend you to read PG’s essay: On Lisp, and (a hard read) SICP.

          As for Haskell, I am a teacher and I teach Haskell. I use Learn you a Haskell and Haskell programming from first principles. Haskell and Lisp are languages that by nature pull CS and math wizards. So is the documentation also written in that way. Hoogle is still one of the best sources of documentation.

          • “If you don’t paint a picture with this specific paint, it’s not a painting”. So if someone were to format the code differently, say put each right bracket on a new line, the compiler would fail?

            Haskell and Lisp are languages that by nature pull CS and math wizards

            They pull them because he learning material is written for them. If the learning material were written for non-wizards, it would attract non-wizards.

            “Learn you a Haskell” is not a good book, IMO. It teaches exactly in the style mentioned. Just look at the part on applicative functors.

            fmap :: (a -> b) -> f a -> f b It says: give me a function that takes an a and returns a b and a box with an a (or several of them) inside it and I’ll give you a box with a b (or several of them) inside it. It kind of applies the function to the element inside the box.

            He has to describe what the function does because the function declaration doesn’t use clear variables or type names. He says the word “box” but writes “f”. Why not just write “box”?

            The entire CS and maths field is filled with people who suck terribly at explaining anything to anybody who doesn’t think like them. Monads aren’t terribly complicated, but the way they are explained is. Every book trying to explain them makes the mistake of going deep first and then zooming out. They explain in excruciatingly minute detail how monads are built, what other complicated concept they are like, and use single letter names for everything in that explanation.

             class (Functor f) => Applicative f where  
            
                 pure :: a -> f a  
            
                 (<\*>) :: f (a -> b) -> f a -> f b
            

            Same here. Then the examples use Just which doesn’t help with readability either. It would read much better if the code were actually literal instead of using shorthands for everything. More mental energy has to go into keeping a mapping table for every letter in the alphabet instead of it being written explicitly, right there.

            It’s why I hate reading Haskell declarations and old code. Programmers back then just used 1-4 characters for everything. char, bool, m_lnr, T, R, I, f, g, h,… As if they were constantly on the run from the last person who had to read and maintain their code.

            You might be a Haskell teacher, but that doesn’t say anything about the quality of your teaching. I play basketball and could even coach a team, but there’s nothing that will say whether I’m a good coach. If I get a team of people who already play well together, speak my lingo, and jive with me, they might think I’m a good coach. But if I get a team of beginners who have never heard my vernacular, can’t understand my mannerisms, and think “tough love” and the cold shoulder make me a dick, they’ll think I suck.

            • littleomid ( littleomid@feddit.org ) 
              link
              fedilink
              English
              arrow-up
              4
              ·
              2 months ago

              My students who did Haskell last year all passed with flying colors. I think the examples above are plenty clear, and the students also found them clear after I explained them, and with enough practice it wasn’t an in issue. I read the literature, practice it, and then use my teaching skills to teach it. It’s my job, and I take pride in what I do.

              I’d say maybe the hypothetical you just needs a good teacher to show how it’s done, or the hypothetical student needs to read it enough till you understand it. In math we also have symbols, in math we also use shorthands. Why not in compsci?

              Bar that, Haskell is just not a language that’s suited as a first language. The literature expects from you to be able to understand technical manuals. You don’t go teaching Rust to 8th graders, you don’t go learning Haskell without knowing at least what currying means.

              As for brackets, you’re free to put them wherever you want; the professional are also free to do what they want, and it’s usually a good idea to adhere to a standard.

              • I remember a promising study about Haskell as a first language several years ago. The much bigger problem is indeed documentation and building a curriculum for beginners than anything about the language itself (currying included – without background from another language you aren’t already stuck in the mental state of “every function is uncurried”).

                Haskell is my favourite language and I like LYAH but at the end of the day OCaml infrastructure for beginners is just better. LearnOCaml in particular. It’s a worse language but I get to focus on the “paradigms” part of my course without having to spend extra time teaching how to jump through Haskell’s hoops. (They’re good hoops, but if I covered them quickly, students wouldn’t see it that way, I think.)

                If we could get LearnHaskell or something and have it as easy to write exercises and configure, I’d seriously consider switching.

    • Alavi ( somegeek@programming.dev ) 
      link
      fedilink
      arrow-up
      4
      ·
      2 months ago

      The polish notation is the simplest thing to wrap you head around. Instead of operations being special syntax exceptions, they’re just functions! Functions that take parameters.

      the only syntax of lisps are (myfun p1 p2 p3)

      Mathematical operations are no exception (unlike otger languages). To make it simpler, think of it like this: + is just an alias (macro) for a function named plus which does addition. (plus 1 2 4 5) is the same as (+ 1 2 4 5). We don’t use infix notation because then that would be a syntactic exepction (like other languages) while this is the only syntax we have in lisp, for everything it’s really simple.

      and also, how is (1 + 2 + 4 + 5) (15 chars) better than (+ 1 2 4 5) (11 chars)? It’s a conceptual shift and once you make it, it makes so much more sense.

      • mlatu ( mlatu@moist.catsweat.com ) 
        link
        fedilink
        arrow-up
        1
        ·
        2 months ago

        i had to try again a couple times too before i got my brain to understand it, also maybe had to find just the right guide (practical common lisp in my case), but now that it’s in there its much easier for me to reason about code using LISP than it was ever in C/++/#, D, Java, Python…