mummy
sokol-rust
| mummy | sokol-rust | |
|---|---|---|
| 7 | 1 | |
| 255 | 52 | |
| - | - | |
| 8.4 | 8.6 | |
| 7 days ago | 11 days ago | |
| Nim | C | |
| MIT License | zlib License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
mummy
- Nim v2.0 Released
- Mummy – web server written in Nim that returns to the ancient ways of threads
-
Nim version 2.0.0 release candidate
Personally this preciseness is just a distraction, but it sounds like you have learned from the constraints and can now take the training wheels off again.
Very curious about those cases, yet to find one myself that was not because of a bad design decision. Though I am also very big on the idea of `ambiguous grammar, rigorous implementation`, for natural language too. (Toki Pona is a somewhat extreme example but the contextual grammar, and holistic minimalism is fascinating)
Not to make it longer than needs to be; But take the example code in this readme: https://github.com/guzba/mummy
Being able to quickly script this without thinking about cases or style on the first pass is a really lovely way of reducing friction imho.
-
Mummy, a new multithreaded HTTP + WebSocket server that returns to the ancient ways of threads
Added a WebSocket chat example here: https://github.com/guzba/mummy/blob/master/examples/chat.nim
sokol-rust
-
Nim v2.0 Released
I maintain auto-generated bindings for my C libraries for Zig and Nim (and Odin and Rust - although the Rust bindings definitely need some love to make them a lot more idiomatic).
I think looking at the examples (which is essentially the same code in different languages) gives you a high level idea, but they only scratch the surface when it comes to language features (things like the Zig code not using comptime features):
Zig: https://github.com/floooh/sokol-zig/tree/master/src/examples
Nim: https://github.com/floooh/sokol-nim/tree/master/examples
Odin: https://github.com/floooh/sokol-odin/tree/main/examples
Rust: https://github.com/floooh/sokol-rust/tree/main/examples
What are some alternatives?
nim-chronos - Chronos - An efficient library for asynchronous programming
questionable - Elegant optional types for Nim
nim-results - Friendly value-or-error type
torrentinim - A very low memory-footprint, self hosted API-only torrent search engine. Sonarr + Radarr Compatible, native support for Linux, Mac and Windows.
fungus - Object variants done like other langugaes
norm - A Nim ORM for SQLite and Postgres
jester - A sinatra-like web framework for Nim.
futhark - Automatic wrapping of C headers in Nim
owlkettle - A declarative user interface framework based on GTK 4
rust - Empowering everyone to build reliable and efficient software.
mvb-opencv - Minimum Viable Bindings to OpenCV for Nim
pixie - Full-featured 2d graphics library for Nim.