44 lines
5.0 KiB
Markdown
44 lines
5.0 KiB
Markdown
|
title: Nimbus
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
# Status Partners with the team behind the programming language Nim
|
|||
|
|
|
|||
|
|
*To bolster research efforts for Nimbus – a sharding client for Ethereum – status.im have partnered with the core team developing the Nim programming language.*
|
|||
|
|
|
|||
|
|
On August 1st, we [posted](https://our.status.im/introducing-nimbus-an/) about our research initiative called Nimbus – a Nim implementation of a sharding client for Ethereum. Today we are pleased to announce our partnership with the team behind the [Nim programming language](https://nim-lang.org/); lead by [Andreas Rumpf](https://github.com/Araq). This partnership will not only support our ongoing sharding research, but promote the continued development of the underlying open source language serving as the basis of our work. The more developed, documented, and robust Nim is, the more in depth our R&D can be. Andreas and team have a strong vision for the future of the programming language and we want to support them in their efforts. This marks our ongoing support for open source projects as well as our commitment to our sharding research.
|
|||
|
|
|
|||
|
|
## Why Nim
|
|||
|
|
We chose to work in Nim because it is a lightweight and efficient programming language that suits itself well to resource restricted devices. It also allows us to better learn the Ethereum protocol, as well as attract highly specialized developers with a deep understanding and appreciation for the advanced language features, such as its powerful meta-programming capabilities that give us the flexibility to meet future needs of creating intuitive domain-specific languages tailored to specific facets of Ethereum 2.0 development.
|
|||
|
|
|
|||
|
|
Finally, the language is backed by a very strong team of talented developers. Andreas started Nim's development in 2006, only two years later the compiler reached the important milestone of being able to compile itself, a process that is known as "bootstrapping". For years now users are deploying Nim applications in production.
|
|||
|
|
|
|||
|
|
Nim can be summarised as combining the very best aspects of the well known programming languages C, Python and Lisp: Nim is as fast as C, as readable as Python and as extensible as Lisp. This aspect makes Nim unique in the large landscape of existing programming languages.
|
|||
|
|
|
|||
|
|
Nim was envisioned from the start as a simple language with a focus on metaprogramming and with Status' support Nim's metaprogramming will not only cover its syntactic elements but also its semantics and its type system.
|
|||
|
|
|
|||
|
|
## The Partnership
|
|||
|
|
Status will support Andreas and the Nim team with funding and resources needed to stay focused on the development of the programming language. The Nim team will add at least 2 paid full-time developers! They will fix bugs, respond to issues, and of course develop the compiler, the standard library as well as its tooling. So far, the language has been supported by the open source community and generous volunteers and donors who believe in the work. This has created a unique commitment to the project by all those involved but has meant a lack of dedicated and focused computer scientists solely focused on its development.
|
|||
|
|
|
|||
|
|
The Status Nimbus team is very familiar with Nim as core Status contributors [Dustin Brody](https://github.com/tersec), [Eugene Kabanov](https://github.com/cheatfate), [Jacek Sieka](https://github.com/arnetheduck), [Mamy Ratsimbazafy](https://github.com/mratsim), [Ryan Lipscombe](https://github.com/coffeepots), [Yuriy Glukhov](https://github.com/yglukhov) and [Zahary Karadjov](https://github.com/zah) are active contributors to the Nim ecosystem. There is already deep integration and collaboration between the Nimbus and Nim teams and this partnership will see even further collaboration and support of each other's work.
|
|||
|
|
|
|||
|
|
## A Look Ahead at the Roadmap
|
|||
|
|
With Status' sponsorship, the Nim team has come up with an ambitious roadmap which makes Nim one of the most exciting languages to watch in the following years. Nim version 1.0 is the long overdue commitment to a stable language core that will preserve backwards compatibility for years to come. There are no hard deadlines to a release date, but a detailed milestone tracking all the issues that need to be resolved for v1.0 is available [here](https://github.com/nim-lang/Nim/milestone/2).
|
|||
|
|
|
|||
|
|
## Beyond the Partnership
|
|||
|
|
In addition to the sponsorship of Nim's ongoing core development there will be a "grants program for Nim". Inspired by Google's Summer of Code, developers will be hired to work on specific Nim-related projects.
|
|||
|
|
|
|||
|
|
Examples for grants:
|
|||
|
|
|
|||
|
|
* Add [Language Server Protocol](https://langserver.org/) support to nimsuggest, for better editor and IDE integration.
|
|||
|
|
* Improve Nim's package manager, "Nimble", to support reproducible builds.
|
|||
|
|
* Improve Nim's tooling so that the result of macro expansions becomes easier to look at.
|
|||
|
|
|
|||
|
|
We look forward to working with Andreas and the team to push the development of Nim.
|
|||
|
|
|
|||
|
|
For more information about Nimbus, join us on [Riot](https://chat.status.im/) or [Github](https://github.com/status-im/nimbus).
|
|||
|
|
|
|||
|
|
You can learn more and get involved with Nim on [Github](https://github.com/nim-lang).
|
|||
|
|
|
|||
|
|
|
|||
|
|
|