torrentinim VS questionable

Check out my project Torrentinim for a popular but simple enough project if you want to taste what Nim is like.

https://github.com/sergiotapia/torrentinim

It's easy to understand code.

Would love to try this. You should provide compiled assets for all major platforms. I don't know how to run this on a Windows machine.

Here's an example how I do it for my project: https://github.com/sergiotapia/torrentinim/blob/master/.gith...

And the releases: https://github.com/sergiotapia/torrentinim/releases

That appears to be a work in progress: https://github.com/sergiotapia/torrentinim/issues/2

Nice. If someone is looking for something less resource hungry, have a look at Torrentinim. It is the successor of Magnetissimo.

Nim's elevator pitch is looks like Python so it's easy to read/write, compiles down to C and then to native binaries, and runs so fast it'll make your head explode.

Here's a project I wrote in Nim that even if you've never even seen Nim before you would understand what's going on. https://github.com/sergiotapia/torrentinim

> 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.

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