home.social

#functionalprogramming — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #functionalprogramming, aggregated by home.social.

fetched live
  1. Thisnis actually starting to look better than I thought.

    Mixing explicit type annotation and choosing some parts to be inferred is some cool shit.

    ----

    A Preview of Roc 0.1.0 by Richard Feldman

    youtube.com/watch?v=a7qEOtkkDb8

    #functionalProgramming #FP #programming #programmingLanguages #roc #roclang

  2. Thisnis actually starting to look better than I thought.

    Mixing explicit type annotation and choosing some parts to be inferred is some cool shit.

    ----

    A Preview of Roc 0.1.0 by Richard Feldman

    youtube.com/watch?v=a7qEOtkkDb8

    #functionalProgramming #FP #programming #programmingLanguages #roc #roclang

  3. Accepted! I'll be talking about bending strongly typed language compilers to your will at the 2026 #IndiaFoss in #Bangalore. #FunctionalProgramming enthusiasts, come join me there. Let's make it IndiaFPoss! 😉

    fossunited.org/c/indiafoss/202

  4. Accepted! I'll be talking about bending strongly typed language compilers to your will at the 2026 #IndiaFoss in #Bangalore. #FunctionalProgramming enthusiasts, come join me there. Let's make it IndiaFPoss! 😉

    fossunited.org/c/indiafoss/202

  5. Tirritate pure #FunctionalProgramming aficionados by denouncing the idea that one can't fix their data structure after buying it as an example of the consumerism propaganda of late stage capitalism.

  6. Tirritate pure #FunctionalProgramming aficionados by denouncing the idea that one can't fix their data structure after buying it as an example of the consumerism propaganda of late stage capitalism.

  7. Since January I've written almost nothing but Elm, and I've been trying to work out why it makes me so happy.

    Partly it's the type system as a creative act rather than a puritan spoiler of fun. Partly it's that exhaustive pattern matching quietly compensates for my terrible working memory — the compiler remembers the cases I'd forget.

    A post about language design, joy, and what your favourite language says about your brain.

    whitebeard.blog/posts/learning

    #Elm #FunctionalProgramming #Programming

  8. Since January I've written almost nothing but Elm, and I've been trying to work out why it makes me so happy.

    Partly it's the type system as a creative act rather than a puritan spoiler of fun. Partly it's that exhaustive pattern matching quietly compensates for my terrible working memory — the compiler remembers the cases I'd forget.

    A post about language design, joy, and what your favourite language says about your brain.

    whitebeard.blog/posts/learning

    #Elm #FunctionalProgramming #Programming

  9. I am starting to become very annoyed with #Guile Scheme because they are so far behind in providing some very important modern SRFIs.

    Of course I could implement these myself and submit a patch, but in the mean time I would have to wait for my patch to be accepted and distributed in the next Guile version. And while I waited I would have to just implement these SRFIs in my own source code for myself. I don’t have time, so I always end up just implementing the APIs that I need for my own project, usually as a wrapper around some other Guile API that does provide that functionality but in a non-standard way.

    For the past two years or so I have kept on running into issues caused by the fact that Guile does not provide SRFI-125 (hash tables) and SRFI-128 (comparators). Guile provides SRFI-69 (the old hash tables) but it doesn’t use comparators, and so the semantics for things like make-hash-table and alist->hash-table in Guile are not compatible with most other R7RS-compliant Scheme implementations. I keep having to go back and update various cond-expand statements to get around this. Some data structures are so fundamental to modern software that you just can’t do without them. Providing these SRFIs should really be a priority.

    Also the following would be really nice to have in Guile, like really soon:

    • SRFI-160: homogeneous numerical vectors, Guile only provides the older version of it, SRFI-4.
    • SRFI-170: POSIX API: Guile provides all of these APIs but not always in a way that follows SRFI-170.
    • SRFI-180: JSON, Guile provides all of these APIs but not fully compatible with SRFI-180.
    • SRFI-181: Custom ports, Guile provides similar features built-in but not in a way that follows SRFI-181.

    #tech #software #Lisp #SchemeLang #Scheme #R7RS #GuileScheme #FunctionalProgramming

  10. I am starting to become very annoyed with #Guile Scheme because they are so far behind in providing some very important modern SRFIs.

    Of course I could implement these myself and submit a patch, but in the mean time I would have to wait for my patch to be accepted and distributed in the next Guile version. And while I waited I would have to just implement these SRFIs in my own source code for myself. I don’t have time, so I always end up just implementing the APIs that I need for my own project, usually as a wrapper around some other Guile API that does provide that functionality but in a non-standard way.

    For the past two years or so I have kept on running into issues caused by the fact that Guile does not provide SRFI-125 (hash tables) and SRFI-128 (comparators). Guile provides SRFI-69 (the old hash tables) but it doesn’t use comparators, and so the semantics for things like make-hash-table and alist->hash-table in Guile are not compatible with most other R7RS-compliant Scheme implementations. I keep having to go back and update various cond-expand statements to get around this. Some data structures are so fundamental to modern software that you just can’t do without them. Providing these SRFIs should really be a priority.

    Also the following would be really nice to have in Guile, like really soon:

    • SRFI-160: homogeneous numerical vectors, Guile only provides the older version of it, SRFI-4.
    • SRFI-170: POSIX API: Guile provides all of these APIs but not always in a way that follows SRFI-170.
    • SRFI-180: JSON, Guile provides all of these APIs but not fully compatible with SRFI-180.
    • SRFI-181: Custom ports, Guile provides similar features built-in but not in a way that follows SRFI-181.

    #tech #software #Lisp #SchemeLang #Scheme #R7RS #GuileScheme #FunctionalProgramming

  11. Working on a silly personal project. That's right! It's #Concur UI for shell scripts!

    #functionalprogramming

  12. Working on a silly personal project. That's right! It's #Concur UI for shell scripts!

    #functionalprogramming

  13. What do #FPIndia gatherings look like?

    Here are a few pictures from a past #Bangalore #Meetup.

    We don't usually take a lot of pictures, but will share some from each meetup going forward.

    #FunctionalProgramming

  14. What do #FPIndia gatherings look like?

    Here are a few pictures from a past #Bangalore #Meetup.

    We don't usually take a lot of pictures, but will share some from each meetup going forward.

    #FunctionalProgramming

  15. So happy to have my package listed here!

    ocaml.org/p/ifs-fractals/1.1.0

    The community feels much friendlier than many others, and its release process is refreshingly centered on real human interactions. You don't simply push a new release and call it a day. Someone actually reviews it. It takes time. Something rare nowadays.

  16. So happy to have my package listed here!

    ocaml.org/p/ifs-fractals/1.1.0

    The #OCaml community feels much friendlier than many others, and its release process is refreshingly centered on real human interactions. You don't simply push a new release and call it a day. Someone actually reviews it. It takes time. Something rare nowadays.

    #OpenSource #FunctionalProgramming #Programming

  17. An assembler written in R5RS Scheme for Intel Architecture

    A person called Jonathan Kraut wrote an #assembler called Sassy in #R5RS #Scheme, which is used as the native code generating phase for the Larceny scheme compiler.

    #tech #Software #SchemeLang #IA32 #FunctionalProgramming #Compiler

  18. An assembler written in R5RS Scheme for Intel Architecture

    A person called Jonathan Kraut wrote an #assembler called Sassy in #R5RS #Scheme, which is used as the native code generating phase for the Larceny scheme compiler.

    #tech #Software #SchemeLang #IA32 #FunctionalProgramming #Compiler

  19. #FPIndia is looking for #meetup hosts in #Bangalore

    Connect with senior devs and architects
    Showcase your engineering culture
    Engage with the community

    Space for ~30 people and a screen, for ~3 hours

    DM or comment!

    #FunctionalProgramming #haskell #elixir #rust #typescript #clojure #formalmethods

  20. #FPIndia is looking for #meetup hosts in #Bangalore

    Connect with senior devs and architects
    Showcase your engineering culture
    Engage with the community

    Space for ~30 people and a screen, for ~3 hours

    DM or comment!

    #FunctionalProgramming #haskell #elixir #rust #typescript #clojure #formalmethods

  21. #FPIndia is looking for #meetup hosts in #Bangalore

    Connect with senior devs and architects
    Showcase your engineering culture
    Engage with the community!

    We need a space for 20 to 40 people and a screen for ~3 hours

    DM or comment!

    #FunctionalProgramming #haskell #elixir #rust #clojure #typescript #scala #purescript #formalmethods

  22. #FPIndia is looking for #meetup hosts in #Bangalore

    Connect with senior devs and architects
    Showcase your engineering culture
    Engage with the community!

    We need a space for 20 to 40 people and a screen for ~3 hours

    DM or comment!

    #FunctionalProgramming #haskell #elixir #rust #clojure #typescript #scala #purescript #formalmethods

  23. I'm curious whether future civilizations are going to look at Nix as something primitive or something advanced

    #Nix #NixOS #functionalprogramming #Linux

  24. I'm curious whether future civilizations are going to look at Nix as something primitive or something advanced

    #Nix #NixOS #functionalprogramming #Linux

  25. I should give a talk titled "Prove, don't validate".

    I talked a little about it this Saturday at the #FPIndia #Bangalore #Meetup

    Follow me to get updates on our next meetup!

    #Haskell #FunctionalProgramming #FormalVerification

  26. I should give a talk titled "Prove, don't validate".

    I talked a little about it this Saturday at the #FPIndia #Bangalore #Meetup

    Follow me to get updates on our next meetup!

    #Haskell #FunctionalProgramming #FormalVerification