#nim has always been focused on providing a compiled statically typed language focusing on efficiency, readability and flexibility.

Version 1.0 marks the beginning of a stable base which can be used in the coming years, knowing that the future versions of Nim won’t break the code you have written with the current version.

https://nim-lang.org/blog/2019/09/23/version-100-released.html

​​Interesting case. This library is 10x faster than requests and has the same API. 93 lines of code, 1 developer, and 0 dependencies.

How is that possible? The secret is that uses #nim under the hood to do all the heavy lifting. And #python API for end users.

https://github.com/juancarlospaco/faster-than-requests

​​> Most people use vim in two stupid dimensions. But not me. I use it in three:

https://github.com/oakes/vim_cubed

#nim

​​Compile #nim Extensions for #python On Import!

Pros:
- Performance: Nim compiles to C
- Reduce cloud computing costs without writing C
- Leverage both language's ecosystems: Python for breadth, Nim for performance.
- Seamless integration with existing Nim code by using the Nimpy library.
- Very low effort to create high-performance Python extensions using Nim.
- 100% transparent to end users (doesn't require Nim compiler).

https://github.com/Pebaz/nimporter

​​Erlang/Elixir NIFs in Nim

Nimler is a library for authoring #erlang and #elixir NIFs in the #nim programming language. It has mostly complete bindings for the Erlang NIF API and some accessories for making writing NIFs easier, including idiomatic functions for converting between Erlang terms and Nim types, and simplifications for using resource objects.

Mostly, Nimler is a minimal, zero-dependency wrapper for Erlang NIF API.

https://github.com/wltsmrz/nimler