questionable
prologue
questionable | prologue | |
---|---|---|
3 | 12 | |
113 | 1,211 | |
2.7% | 0.8% | |
7.0 | 5.1 | |
22 days ago | 12 days ago | |
Nim | Nim | |
GNU General Public License v3.0 or later | Apache License 2.0 |
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.
questionable
-
Nim v2.0 Released
> You can also not really have productive and well-fitting errors-as-values in a language that emphasizes UFCS
Eh, https://github.com/arnetheduck/nim-results and associated syntax from https://github.com/codex-storage/questionable would beg to disagree. Nim's stdlib does not have productive and well-fitting errors because it suffers from inertia and started far before the robust wonders of recoverable error handling via errors-as-types entered the mainstream with Rust (IMO: and refined with Swift). Option/Result types are fantastic and I do so wish the standard library used them: but it's nothing a (very large) wrapper couldn't provide, I suppose.
I do strongly think that other languages are greatly missing out on UFCS and I miss it dearly whenever I go to write Python or anything else. I'm not quite sure how you think UFCS would make it impossible to have good error handling? Rust also has (limited, unfortunately) UFCS and syntax around error handling does not suffer because of it. If by errors-as-values you mean Go-style error handling, I quite despise it - I think any benefits of the approach are far offset by the verbosity, quite similarly to Java's checked exceptions.
-
Stop Building on Corporate-Controlled Languages
If exceptions aren’t your cup of tea, look into using stew/results and questionable instead:
https://github.com/status-im/nim-stew/blob/master/stew/resul...
https://github.com/status-im/questionable#readme
Re: std/db_sqlite, your probably better off using sqlite3_abi:
https://github.com/arnetheduck/nim-sqlite3-abi#readme
prologue
- Nim v2.0 Released
-
prologue VS happyx - a user suggested alternative
2 projects | 24 May 2023
-
Setup a Website with Nim
If you want to try an alternative to Jester, Prologue is very nice to use: https://github.com/planety/prologue
- Prologue – Powerful and flexible web framework written in Nim
-
Nim Version 1.6 Released
Well no language is perfect, but Nim can be used in almost every domain because of it's compilation targets(C, C++, JS) and it's fast compile times(who needs interpretation when compile times are that fast!):
* Shell scripting, I still assume most people will just use Bash tho: https://github.com/Vindaar/shell
* Frontend: https://github.com/karaxnim/karax or you could bind to an existing JS library.
* Backend: For something Flask-like: https://github.com/dom96/jester or something with more defaults https://github.com/planety/prologue
* Scientific computing: the wonderful SciNim https://github.com/SciNim
* Blockchain: Status has some of the biggest Nim codebases currently in production https://github.com/status-im?q=&type=&language=nim&sort=
* Gamedev: Also used in production: https://github.com/pragmagic/godot-nim and due to easy C and C++ interop, you get access to a lot of gamedev libraries!
* Embedded: this is a domain I know very little about but for example https://github.com/elcritch/nesper or https://github.com/PMunch/badger for fun Nim+embedded stuff!
Most of the disadvantages come from tooling and lack of $$$ support.
-
Good web framework for Nim?
It doesn't https://github.com/planety/prologue/blob/devel/prologue.nimble
-
How to create a file upload server?
Jester is really great but I feel Prologue should get some attention too.
-
Learning Nim: Web Server with Jester and Norm [video]
Nice! I want to also suggest the Prologue framework - here are the docs
-
One Nim web framework to rule over all styles
Prologue is a great web framework in the Nim world. However, Prologue framework tries to avoid using macros. It is intended to reduce magic and reduce surprise. Macros could save you from redundant codebases. At the mean time, it could bring surprise. This article talks about how to extend the routing style outside Prologue without invading inside the web framework.
-
Prologue: A powerful web framework written in Nim
Prologue is a powerful and extensible web framework written in Nim language.
What are some alternatives?
pekko - Build highly concurrent, distributed, and resilient message-driven applications using Java/Scala
jester - A sinatra-like web framework for Nim.
nim-chronos - Chronos - An efficient library for asynchronous programming
awesome-nim - A curated list of awesome Nim frameworks, libraries, software and resources.
owlkettle - A declarative user interface framework based on GTK 4
nim-playground-frontend - The front-end for https://play.nim-lang.org
v - Write Nim only with 'v'
Nim - Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
sokol-rust - Rust bindings for the sokol headers (https://github.com/floooh/sokol)
httpbeast - A highly performant, multi-threaded HTTP 1.1 server written in Nim.
sokol-zig - Zig bindings for the sokol headers (https://github.com/floooh/sokol)
norm - A Nim ORM for SQLite and Postgres