Simon Peyton Jones - A History of Haskell: being lazy with class

Поделиться
HTML-код
  • Опубликовано: 7 сен 2024

Комментарии • 7

  • @David-2501
    @David-2501 4 года назад +14

    Oh my, those are quite the (IMO) legendary figures in one room! I'm pretty sure that if you google any of the mentioned names of the people in that room, you'll get a wiki page full of accomplishments!

  • @Kram1032
    @Kram1032 8 лет назад +10

    Funny how these things have changed. Haskell _still_ isn't exactly mainstream but it has picked up quite prominent, explicitly product-focues rather than academic users. And dependent types are right around the corner and presumably will revolutionize a lot of how Haskell is written.

    • @unidorsalicosahedron7416
      @unidorsalicosahedron7416 7 лет назад +1

      Yes, DemonLordChaos! Here's someone who gets it!
      As for Kram1032, I suggest you have a look at "Simon Peyton Jones - Haskell is useless". That video should be in the recommendations for this video and it should answer your concerns.

    • @Kram1032
      @Kram1032 7 лет назад

      I didn't voice any concerns? And I already saw the video you suggest.

    • @unidorsalicosahedron7416
      @unidorsalicosahedron7416 7 лет назад

      Kram1032
      Nevermind then.

    • @Evan490BC
      @Evan490BC 7 лет назад

      I'm not sure what you mean by "Fortran is so obsessed with basic addition in loops". What's wrong with ``A + B``, where A and B are first-class arrays (this is legal Fortran. Fortran is an *array* language, much like Matlab)? Or a function definition like ``pure function distance(p, q)``, with side-effects disallowed? How about Modules, operator overloading with user defined operators, abstract data types, classes, etc? Are we talking about a different language? (Not lambdas (yet) unfortunately, though.)

  • @karolyhorvath7624
    @karolyhorvath7624 6 лет назад +6

    39:59 Type safety - the next level