ADadriansieradzki·Apr 8, 2025Submission
Nu: F# Functional Game Engine Worth Your Attention
3 points · Open discussionbryanedds
Nu
F#2014–2025
bryanedds / Nu
Nu
Repository hosting the functional Nu Game Engine and related projects.
7Distinct people
9Mentions
1Explicit recommenders
1.4KGitHub stars
What to know before exploring
What it is
Repository hosting the functional Nu Game Engine and related projects.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
A lot of Aml code can be found in the Stdlib, which is here - https://github.com/bryanedds/FPWorks/tree/master/Aml/Aml/Aml... To make the code more readable, I recommend…
DrDimension used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year9 dated mentions
Observed mentions: 2014-09-20 20:31:17 UTC to 2025-04-08 11:02:58 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 2 | 2 | 0 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
9 sourcesNu Game Engine: Practical functional Game Engine written in F#
3 points · Open discussionThe Nu game engine might interest you. There's also FuncUI for app dev which is F# + MVU running on Avalonia.
https://github.com/bryanedds/Nu
https://github.com/fsprojects/Avalonia.FuncUI
In Iced: A cross-platform GUI library for Rust, inspired by ElmHave you heard of the Nu game engine[1]? It is a FRP-based game engine for F#.
[1] https://github.com/bryanedds/Nu
In Game Programming Patterns (2014)Finally, Nu Game Engine v1.0.0.0
1 points · Open discussionIterative Functional Reactive Programming with the Nu Game Engine: An Exp Report
This is an experience report on the design and usage of the Nu Game Engine, a purely-functional 2D game engine written in F# -
http://goo.gl/PRHqOp
Original link here -
https://github.com/bryanedds/FPWorks/blob/master/Nu/Documentation/Iterative%20Func…
Synopsis
The Nu Game Engine certainly qualifies as 'functional reactive' in that -
1) it is reactive in that it uses user-defined events to derive successive simulation states.
2) it is functional in that is uses pure functions everywhere, even in the event system.
However, I cannot describe it as the typical first-order or higher-order FRP system since it uses neither continuous nor discrete functions explicitly parameterized with time. Instead it uses a classically-iterative approach to advancing game states that
Read the rest
is akin to the imperative tick-based style, but implemented with pure functions.
Thus, I gave it the name of 'Iterative FRP'. It's a purely-functional half-step between classic imperative game programming and first / higher-order FRP systems. This document discusses the major plusses and minuses to using this 'iterative' FRP style.
A lot of Aml code can be found in the Stdlib, which is here - https://github.com/bryanedds/FPWorks/tree/master/Aml/Aml/Aml...
To make the code more readable, I recommend grabbing TextPad and configuring the syntax highlighter using the files here - https://github.com/bryanedds/FPWorks/tree/master/Aml/Plugins...
Thank you kindly for taking an interest in my work. I will attend to your pull request immediately.
In Show HN: Practical, Pure Functional Game EngineI think you should add a code example to the README, to communicate the flavor of the engine. Seeing code reassures me that the engine and its API is not unnecessarily verbose. `BlazeDispatchers.fs`’s `EnemyModule.tickHandler (https://github.com/bryanedds/FPWorks/blob/master/BlazeVector...) would be a good example, as it also demonstrates the engine’s functional style of being passed and returning a `world`. You should also link to the folder https://github.com/bryanedds/FPWorks/tree/master/BlazeVector... right below the code snippet so that people can easily see more code examples and see the structure of a whole program’s code.
Also, after reading that you have a custom Ianguage (Aml), I wanted to see what code looks like in this language, but I couldn’t find any code examples. I even downloaded `AmlSpec.rtf`, but all I saw when scannin
Read the rest
g through it was one-line examples to show the syntax, not real examples that show when and why you would use it. If you have examples, you should link to them from where you talk abut Aml in the README.
(I also created a pull request to improve the formatting in `AmlSpec.rtf`: https://github.com/bryanedds/FPWorks/pull/6 .)
Show HN: Practical, Pure Functional Game Engine
29 points · Open discussion