43
What makes Lisp difficult to read? (paultm.nl)
submitted 1 month ago by to c/programming@programming.dev
39 comments fedilink hide all child comments
 

cross-posted from: https://lemmy.bestiver.se/post/1365818

Comments

you are viewing a single comment's thread
view the rest of the comments
[+] 7 points 1 month ago* (last edited 2 weeks ago) (9 children)
[deleted]
  • permalink
  • fedilink
  • source
  • hideshow 9 child comments
    •
  • [–] [S] 3 points 1 month ago (8 children)

    Did you read the article? This has nothing to do with familiarity.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [+] 3 points 1 month ago* (last edited 2 weeks ago) (6 children)
    [deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] [S] 0 points 1 month ago (5 children)

    "They're wrong, that's the way it is". Great argument. Very convincing.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 2 points 1 month ago* (1 child)

    Their first comment provided reasoning. This "because that's the way it is" framing is unfair.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] [S] 1 point 4 weeks ago

    The article is 90% about brackets and Polish notation is nearly a footnote. How is the reasoning that "it's mostly familiarity" sound? When I call doSomething(param, arg, whatever) moving over the left bracket a word isn't going to confuse people because of "familiarity".

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 1 month ago

    well, if familiarity can be ruled out, surely there is a quadruply-blind study then? how many participants were there? you need to test teaching lisp first then c and on another group the other way around. you also need to have groups of untrained people and show lisp first, then c, another group for the other way around.

  • permalink
  • fedilink
  • source
  • parent