Latest posts tagged with #Functionalprogramming on Bluesky
This sounds like a really interesting PhD course at Chalmers: “Functional Programming and Climate Impact Research”, by Patrik Jansson:
https://github.com/DSLsofMath/FPClimate
After completion of the course the student should be able to:
Use functional programming specification / implementation […]
Readings shared March 09, 2026. jaalonso.github.io/vestigium/po... #AI #AI4Math #CategoryTheory #CoqProver #Emacs #FunctionalProgramming #Haskell #ITP #IsabelleHOL #LambdaCalculus #LeanProver #Lisp #Math #Physics #RocqProver
Welcome Magda Stożek as the #Scalarconf 2026 speaker!
🎙️ Flexible Modeling: Keeping Your Domain Pure with Scala 3
The full Scalar agenda is ready and waiting for you on our website!
🎟️ Grab your ticket here: scalar-conf.com/tickets
#scala #functionalprogramming
The floor is magma. ~ Alexandre Esteves. github.com/alexfmpe/sem... #Haskell #FunctionalProgramming
Lambda calculus for dummies: The Church encoding. youtu.be/CL1LAKMsyKg #LambdaCalculus #FunctionalProgramming
Category theory for programming. ~ Benedikt Ahrens, Kobe Wullaert. arxiv.org/abs/2209.012... #CategoryTheory #Haskell #LeanProver #FunctionalProgramming
Composing Software: An Exploration of Functional Programming and Object Composition in JavaScript by Eric Elliott is the featured course on Leanpub!
Link: leanpub.com/courses/lean...
#ComputerProgramming #FunctionalProgramming #Javascript #Software #SoftwareEngineering #SoftwareArchitecture
OOP Is A Construct Of Oppression Installed By The Bourgeoisie
OOP Is A Construct Of Oppression Installed By The Bourgeoisie
#oop #Objectorientedprogramming #Functionalprogramming #Cleancode #Refactoring
programmerhumor.io/programming-memes/oop-is...
Readings shared March 04, 2026. jaalonso.github.io/vestigium/po... #AI #AI4Math #CoqProver #FunctionalProgramming #Haskell #ITP #LeanProver #Math #RocqProver
Monuses and heaps. ~ Donnacha Oisín Kidney. doisinkidney.com/posts/2026-0... #Haskell #FunctionalProgramming
New tale: talesfrom.dev/blog/the-amb... in which we see developers and architects interpreting diagrams.
#objectorienteddesign #functionalprogramming #empathydrivendesign #domaindrivendesign #softwarearchitecture #softwaredesign #collaborativesoftwaredesign
📖 A new book by Noel Welsh is in the making. Read a preview about the approaches to dependency injection in FP and OOP to fully understand the connection between them. 👇 buttondown.com/functionalpr... #scala #functionalprogramming
Just joined Bluesky! Senior F# engineer based in Barcelona — 10+ years building production systems with DDD, event sourcing, and Ports & Adapters. Excited to connect with the functional programming community here.
#fsharp #dotnet #functionalprogramming
Turn branching C# into clear, composable pipelines with practical function composition patterns from Mori. See how small pure functions lead to code that is easier to test, maintain, and optimize.
#csharp #dotnet #functionalprogramming
Starting a new video series on #CategoryTheory. Please provide feedback. Brickbats welcome, especially of the constructive kind! #FunctionalProgramming
www.youtube.com/watch
Starting a new video series on #CategoryTheory. Please provide feedback. Brickbats welcome, especially of the constructive kind! #FunctionalProgramming
www.youtube.com/watch?v=aKIu...
Common Lisp Tamagotchi development log.
starting to actually lay down some code now...
#lisp #commonlisp #functionalprogramming
Readings shared February 24, 2026. jaalonso.github.io/vestigium/po... #AI4Math #ATP #Agda #CoqProver #FunctionalProgramming #Haskell #ITP #IsabelleHOL #LLMs #LeanProver #Math #Reasoning #Vampire
Haskell meets Evariste. ~ Paulo R. Pereira, Jose N. Oliveira. arxiv.org/abs/2602.168... #Haskell #FunctionalProgramming
Welcome Andrei Kucharavy as the #Scalarconf 2026 speaker!
🎙️ Safer Code with LLMs: Scala Types Silver Bullet?
The full Scalar agenda is ready and waiting for you on our website!
🎟️ Grab your ticket here: scalar-conf.com/tickets
#scala #functionalprogramming
![An entry point for Nix stuff.
# Writing your first flake
Your flake is the entry point to your application built and run with nix.
Your flake is a function from `inputs` (which consist of urls for getting package sets) to `outputs`, with outputs being one big _attribute set_.
This `outputs` _attribute set_ looks something like this (very much like a JSON object):
```nix
# outputs
{
apps = { ... };
checks = { ... };
devShells = { ... };
formatter = { ... };
legacyPackages = { ... };
nixosConfigurations = { ... };
nixosModules = { ... };
overlays = { ... };
packages = { ... };
}
```
Every key in here is a special, magic key that Nix interprets in a certain way.
For the minimal (non-functional) flake:
```nix
{
inputs = {};
outputs = {...}: {};
}
```
all of them are empty.
Through populating them, we give our Nix Flake additional capabilities.
The first capability to give our Nix Flakes is normally a _development shell_.
In Nix Language, we create this like this:
```nix title="flake.nix"
{
inputs = {
nixpkgs.url = "github:nixos/nixpkgs?ref=nixos-unstable";
};
outputs = { nixpkgs, ... }: {
devShells.x86_64-linux.default = nixpkgs.legacyPackages.x86_64-linux.mkShell {};
};
}
```
And run it via `nix develop` (getting it? The `devShells` output gets run by `nix develop`):
```shell
> nix develop
(nix-shell-env)>
```
But that doesn't do anything yet.
For it to do something we need to add something into the devshell:
```nix title="flake.nix" del={7} ins={8-10}
{
inputs = {
nixpkgs.url = "github:nixos/nixpkgs?ref=nixos-unstable";
};
outputs = { nixpkgs, ... }: {
devShells.x86_64-linux.default = nixpkgs.legacyPackages.x86_64-linux.mkShell {};
devShells.x86_64-linux.default = nixpkgs.legacyPackages.x86_64-linux.mkShell {
packages = [ nixpkgs.legacyPackages.x86_64-linux.hello ];
};
};
}
```
(Run `nix develop`, and then we have the `hello` executable available.):
```shell
> nix develop
(nix-shell-env)> hello
Hello, world!
```
Let's clean this up a bit, and then we're done for now.
There's lots of repetition in the current file, and the solution to this is not as easy as inserting a `let` block.
The accepted and easily extensible solution for this is flake-parts, but their homepage is pretty hard to understand at first.
We want to translate our example to this:
```nix title="flake.nix"
{
inputs = {
nixpkgs.url = "https://github.com/nixos/nixpkgs?ref=nixos-unstable";
};
outputs = inputs@{ flake-parts, ... }:
flake-parts.lib.mkFlake { inherit inputs; } {
systems = [ "x86_64-linux" "aarch64-linux" "aarch64-darwin" "x86_64-darwin" ];
perSystem = { pkgs, ... }: {
devShells.default = pkgs.mkShell {
packages = [ pkgs.hello ];
};
};
};
}
```
This even has the benefit that it will work on all the systems specified.
<Draft>
# Evaluated Flake top level
You can inspect your flake like this:
```shell
nix repl .
> :load-flake . # shorthand ':lf .'
```
```nix
{
_type = "flake";
inputs = { ... };
outputs = { ... };
sourceInfo = { ... };
}
```
</Draft>
<References>
<ReferenceLink href="https://www.youtube.com/watch?v=JCeYq72Sko0">vimjoyer flakes guide</ReferenceLink>
</References>](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:fzyhtjbjqeoj2pmjajl5ehou/bafkreifjretp7fvufhufqv2hnfgdfcuykkpse7saigqzsdfq4vhnqcaeru)
An entry point for Nix stuff. # Writing your first flake Your flake is the entry point to your application built and run with nix. Your flake is a function from `inputs` (which consist of urls for getting package sets) to `outputs`, with outputs being one big _attribute set_. This `outputs` _attribute set_ looks something like this (very much like a JSON object): ```nix # outputs { apps = { ... }; checks = { ... }; devShells = { ... }; formatter = { ... }; legacyPackages = { ... }; nixosConfigurations = { ... }; nixosModules = { ... }; overlays = { ... }; packages = { ... }; } ``` Every key in here is a special, magic key that Nix interprets in a certain way. For the minimal (non-functional) flake: ```nix { inputs = {}; outputs = {...}: {}; } ``` all of them are empty. Through populating them, we give our Nix Flake additional capabilities. The first capability to give our Nix Flakes is normally a _development shell_. In Nix Language, we create this like this: ```nix title="flake.nix" { inputs = { nixpkgs.url = "github:nixos/nixpkgs?ref=nixos-unstable"; }; outputs = { nixpkgs, ... }: { devShells.x86_64-linux.default = nixpkgs.legacyPackages.x86_64-linux.mkShell {}; }; } ``` And run it via `nix develop` (getting it? The `devShells` output gets run by `nix develop`): ```shell > nix develop (nix-shell-env)> ``` But that doesn't do anything yet. For it to do something we need to add something into the devshell: ```nix title="flake.nix" del={7} ins={8-10} { inputs = { nixpkgs.url = "github:nixos/nixpkgs?ref=nixos-unstable"; }; outputs = { nixpkgs, ... }: { devShells.x86_64-linux.default = nixpkgs.legacyPackages.x86_64-linux.mkShell {}; devShells.x86_64-linux.default = nixpkgs.legacyPackages.x86_64-linux.mkShell { packages = [ nixpkgs.legacyPackages.x86_64-linux.hello ]; }; }; } ``` (Run `nix develop`, and then we have the `hello` executable available.): ```shell > nix develop (nix-shell-env)> hello Hello, world! ``` Let's clean this up a bit, and then we're done for now. There's lots of repetition in the current file, and the solution to this is not as easy as inserting a `let` block. The accepted and easily extensible solution for this is flake-parts, but their homepage is pretty hard to understand at first. We want to translate our example to this: ```nix title="flake.nix" { inputs = { nixpkgs.url = "https://github.com/nixos/nixpkgs?ref=nixos-unstable"; }; outputs = inputs@{ flake-parts, ... }: flake-parts.lib.mkFlake { inherit inputs; } { systems = [ "x86_64-linux" "aarch64-linux" "aarch64-darwin" "x86_64-darwin" ]; perSystem = { pkgs, ... }: { devShells.default = pkgs.mkShell { packages = [ pkgs.hello ]; }; }; }; } ``` This even has the benefit that it will work on all the systems specified. <Draft> # Evaluated Flake top level You can inspect your flake like this: ```shell nix repl . > :load-flake . # shorthand ':lf .' ``` ```nix { _type = "flake"; inputs = { ... }; outputs = { ... }; sourceInfo = { ... }; } ``` </Draft> <References> <ReferenceLink href="https://www.youtube.com/watch?v=JCeYq72Sko0">vimjoyer flakes guide</ReferenceLink> </References>
Especially this here for Nix Flakes :)
#Nix #Simplicity #FunctionalProgramming
# Install Nix The installer on the website sucks (doesn't work with SELinux, for example), but there is a community-maintained one: ```shell curl -fsSL https://artifacts.nixos.org/nix-installer | sh -s -- install ``` With that completed, go write your first Nix Flake
I've added a bit more barebones Nix stuff that can be confusing at first :)
#Nix #OS #ProgrammingLanguage #nixpkgs #NixOS #FunctionalProgramming #DeclarativeProgramming
Readings shared February 19, 2026. jaalonso.github.io/vestigium/po... #AI4Math #ATP #CSLib #CompSci #Dedukti #FunctionalProgramming #Haskell #ITP #IsabelleHOL #LLMs #LeanProver #Math #Mizar #RocqProver #Vampire
Composing Software: An Exploration of Functional Programming and Object Composition in JavaScript leanpub.com/courses/lean... by Eric Elliott is the featured course on the Leanpub homepage! leanpub.com #ComputerProgramming #FunctionalProgramming #Javascript #Software #SoftwareEngineering
#Exercitium: Matriz zigzagueante. jaalonso.github.io/exercitium/p... #Haskell #FunctionalProgramming #Math
#Exercitium: Mínimo número de cambios para igualar una lista. jaalonso.github.io/exercitium/p... #Haskell #FunctionalProgramming
#Exercitium: Diagonales secundarias de una matriz. jaalonso.github.io/exercitium/p... #Haskell #FunctionalProgramming #Math
Functional Programming in Java: Valhalla, Pattern Matching, and Records Java’s pragmatic evolution: borrowing functional programming’s best ideas while maintaining backward compatibility Java i...
#Core #Java #FunctionalProgramming #Java #ProjectValhalla
Origin | Interest | Match
Haskell Wizard leanpub.com/b/haskell-wi... by Alejandro Serrano Mena is the featured bundle on the Leanpub homepage! leanpub.com #Haskell #FunctionalProgramming
Find it on Leanpub!
