nico VS nimbus-eth2

I think everything depends on the scale of your ideas, see https://johanpeitz.itch.io/picocad You can make something similar with Nico https://github.com/ftsf/nico :)

Game framework: Nim + Pico-8 = Nico

I love making games with Nico: https://github.com/ftsf/nico

Concise and readable, small binaries, fast compile times, native performance, zero-overhead interop lets you reuse code in C, C++, JS, Objective-C, Python... Does a programming language have these fantastic features? Of course, Nim language does have the features I have been dreaming about. And what is the goal of Nim language? Simply put, the goal is "one language to rule them all", from shell scripting to web frontend and backend, scientific computing, deep learning, blockchain client, gamedev, embedded.

Something to look at if you want to encourage simple game development is supporting PICO-8 [0], or the compiled Nim version Nico [1].

[0]: https://www.lexaloffle.com/pico-8.php?page=faq

[1]: https://github.com/ftsf/nico

Some more fun high level frameworks:

- HaxeFlixel (https://haxeflixel.com/) (Extremely portable)

- Phaser (https://phaser.io/) (HTML5 framework)

- Nico (https://github.com/ftsf/nico) (The PICO-8 API in Nim)

- Pixel Vision 8 (https://pixelvision8.github.io/PixelVision8Website/) (Another fantasy console)

Agreed! There's a couple of fairly large projects in Nim: https://nimbus.team/ (https://github.com/status-im/nimbus-eth2) or https://github.com/zedeus/nitter

Though there's still friction points I've been happy seeing the ecosystem grow lately. The compiler has seen a lot of bug fixes lately too which helps.

Pretty big update for Nimbus out today, it's been a long time coming: https://github.com/status-im/nimbus-eth2/releases/tag/v23.6.0

consensus client/execution client -> ERIGON v2.45.2 and NIMBUS v23.5.1

In the same year their beacon chain client followed Bellatrix (Merge) and Capella upgrades without a hitch, which is in many ways more impressive than a messenger.

Nimbus claims to have a solution to the loss of finality problem that was caused by old attestations, by dramatically speeding up the verification of those attestations: https://github.com/status-im/nimbus-eth2/pull/4911

Seems they just released 23.5.0, to fix many of the issues we've been having: https://github.com/status-im/nimbus-eth2/releases/tag/v23.5.0

https://github.com/status-im/nimbus-eth2 69 contributors

Daily Goerli: Was getting a lot of missed attestations with nimbus and after some back and forth with tersec, we confirmed that timeouts communicating with web3signer were the culprit. A fix should be merged soon.