Conversation

Notices

1. Embed this notice
   Paul Cantrell (inthehands@hachyderm.io)'s status on Wednesday, 03-May-2023 07:41:01 JST Paul Cantrell

   Oh hey, my #Minnebar17 talk is online! Is it good? Not sure, haven’t watched it! But here it is!

   https://www.youtube.com/watch?v=3aw7777DS58

   “The idea that removing features can make programming languages better is both surprising and exciting. What programming language features that we consider essential today might be the next GOTO, withering and vanishing from high-level languages of the future?”

   #Minnebar

   • Embed this notice
     A Bitwise (abitwise@hachyderm.io)'s status on Wednesday, 03-May-2023 12:50:31 JST A Bitwise

     in reply to

     @inthehands Nice work! It resonates with my personal journey with language features. Minus direct memory acces which I haven’t had the (mis)fortune of using very much.

   • Embed this notice
     A Bitwise (abitwise@hachyderm.io)'s status on Wednesday, 03-May-2023 12:50:42 JST A Bitwise

     in reply to

     @inthehands Also, this feels like the lead-up for one-on-ones after the talk like “hey, have you ever tried… <gets quiet> functional programming?”

   • Embed this notice
     Paul Cantrell (inthehands@hachyderm.io)'s status on Wednesday, 03-May-2023 14:06:32 JST Paul Cantrell

     in reply to

     • Mark Gritter

     @markgritter
     Yup. Swift’s protocol extensions (which AFAICT are more or less ML typeclasses, but I’m fuzzy on many details) seem like a major step forward.

   • Embed this notice
     Mark Gritter (markgritter@mathstodon.xyz)'s status on Wednesday, 03-May-2023 14:06:33 JST Mark Gritter

     in reply to

     @inthehands Very nice!

     I'm frustrated by how long we've heard "use composition not inheritance" and yet language support for composition is still so poor. (I like what Swift does -- but my day-to-day language right now is Go and like everything else in Go the solution is "write a bunch of boilerplate so that the function names match up.")

   • Embed this notice
     Paul Cantrell (inthehands@hachyderm.io)'s status on Wednesday, 03-May-2023 14:09:01 JST Paul Cantrell

     in reply to

     • Paul Himes

     @paulhimes It’s basically “Swift optionals!”

     The big insight from that section is that the thing optionals get right that null gets wrong is that null violates LSP:

   • Embed this notice
     Paul Himes (paulhimes@mastodon.social)'s status on Wednesday, 03-May-2023 14:09:02 JST Paul Himes

     in reply to

     @inthehands Fantastic talk! I’d love to hear the null bit.

   • Embed this notice
     Paul Cantrell (inthehands@hachyderm.io)'s status on Wednesday, 03-May-2023 14:11:55 JST Paul Cantrell

     in reply to

     • A Bitwise

     @abitwise I mean, I explicitly plug Elm in the talk, so…yeah!

     And part of what I’m alluding to with the “as-if copied” bit at the end is the emerging new consensus (exemplified by Swift and Rust) that if you have types with value semantics, you can do familiar imperative programming and still secretly be doing functional programming.

   • Embed this notice
     Sven A. Schmidt (finestructure@mastodon.social)'s status on Wednesday, 03-May-2023 22:07:33 JST Sven A. Schmidt

     in reply to

     @inthehands Great talk, loved it!

   • Embed this notice
     Paul Cantrell (inthehands@hachyderm.io)'s status on Wednesday, 03-May-2023 22:07:33 JST Paul Cantrell

     in reply to

     • Sven A. Schmidt

     @finestructure Thanks, Sven!

   • Embed this notice
     Gaston Rampersad (gastonrampersad@mastodon.social)'s status on Wednesday, 03-May-2023 22:09:11 JST Gaston Rampersad

     in reply to

     • Sven A. Schmidt

     @inthehands @finestructure thanks for sharing, this was a very good watch. Great presentation, Paul.

   • Embed this notice
     Paul Cantrell (inthehands@hachyderm.io)'s status on Wednesday, 03-May-2023 22:09:11 JST Paul Cantrell

     in reply to

     • Gaston Rampersad

     @gastonrampersad Thanks!