RFCs
v
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.
RFCs
- Nim Sum types, 2024 variant
- Nim Roadmap 2024 and Beyond
- Nim v2.0 Released
-
Contribute to the Python-like Nim language
compiler support for object construction shorthand
-
Nim 2.0.0 RC2
Well, maybe not writing. Occasionally low-level C libraries - especially those that deal with keyboard input - decide to provide identifiers differing only in case... There's a WIP RFC for providing a way to deal with identifiers that need to be verbatium by surrounding them with backticks, though.
https://github.com/nim-lang/RFCs/issues/477
- please comment on "It totally sounds like the n-word" as well
- Nim goto intermediate representation (NGIR)
-
My Nim Development Weekly Report (3/12)
Following The Roadmap 2023 for community building , you could join us in the matrix space where we discuss how to build a community. We appreciate doable suggestions and helps, such as improving the workflow, implementing the roadmap, suggesting doable tasks, reviewing code from contributors. United we stand. We shall work together to make the community thrive.
- Nim Roadmap 2023
-
My Nim Development Weekly Report (2/19)
First of all, the Nim development follows The Roadmap 2023, which specifies what features might be implemented or removed in 2023. As we can see, completing incremental compilation and recursive module dependencies might be the most important tasks to be done in 2023. You might subscribe to the roadmap and write down your expectations of Nim in 2023 there.
v
-
V Language Review (2023)
Their site is clearly showing the language is in beta. The V documentation also states that autofree is WIP, and to use the GC instead. This isn't a corporate created language, but looks to be a true volunteer open source effort from people around the world.
Their community, in comparison to others, even has their discussions open and open threads for criticism[1]. These
[1]https://github.com/vlang/v/discussions/7610
-
Towards memory safety with ownership checks for C
V also has this https://github.com/vlang/v/blob/master/doc/docs.md#embed_fil...
- Vlang Release v0.4.4
- Vox: Upcoming open-source browser engine in V
- Building a web blog in V & SQLite
- bultin_write_buf_to_fd_should_use_c_write
- The V Machine Learning Roadmap and Ecosystem
-
Show HN: A new stdlib for Golang focusing on platform native support
Goroutines was the selling point for me until they decided to introduce telemetry in their toolchain; that was what forced me to stop using Golang as a whole.
About GC, I would say: if you implement C++'s RAII mechanism to replace garbage collection, then I believe this project will have a bright future.
My final question is the following: how `pcz` compares to V language, from a syntax's perspective [1]?
[1] https://github.com/vlang/v
- Hopefully, the V developers will establish a relationship with Microsoft.
-
The V Programming Language 0.4
V has the right to exist, have its supporters, and do things its own way. The creator and developers of V, from what I have seen, has always responded well to constructive criticism. Their language has discussions opened at their GitHub, unlike those for various other languages. They even have a thread for what people don't like and want improved about the language[1], again, something many other languages don't have.
A lot of what was going on initially, was coming from obvious competitors, to include being uncivil, inflammatory, and insulting. The initial "criticism" was not so much that, but false accusations of the language being a scam, vaporware, fraud, or didn't really exist. To include attacks and jealousy about its funding and having supporters. This was not any kind of "valid" criticism, that the creator or contributors of the language could reason about.
The "criticism" never died down, but rather after V was open-sourced and established itself on GitHub. The initial series of false accusations could not stand nor could the support it was getting be stopped. So, the rhetoric and targets shifted to whatever could be found to go after on the newly released alpha version of the language and its new website. In that new mix of what was being thrown at it, there were indeed some very valid criticisms, as can be found with any new language.
Constructive and valid criticism, is not the same as insults, trolling, misinformation, rivalry, or false accusations. There is clearly a difference. It's disingenuous to pretend something from one group is the same as the other, or that the intent behind what is being done is not different.
[1] https://github.com/vlang/v/discussions/7610
What are some alternatives?
nimskull - An in development statically typed systems programming language; with sustainability at its core. We, the community of users, maintain it.
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
nimforum - Lightweight alternative to Discourse written in Nim
go - The Go programming language
nim-chronos - Chronos - An efficient library for asynchronous programming
Odin - Odin Programming Language
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).
shady - Nim to GPU shader language compiler and supporting utilities.
sokol - minimal cross-platform standalone C headers
cligen - Nim library to infer/generate command-line-interfaces / option / argument parsing; Docs at
hn-search - Hacker News Search