Datamancer VS nimskull

I have been using Nim for all of my recent data munging and analysis. There's https://github.com/Vindaar/ggplotnim for plots (among others) and everything else has just been normal code. There's also https://github.com/SciNim/Datamancer if you need something more like tidyverse.

Check out Datamancer for your Pandas equivalent. If I recall correctly it does have the ability to read/write csv. If that doesn't suite you, there is a Python/Nim bridge called Nimpy. I do a lot of machine learning projects and have to use OpenCV and some other things from python because it doesn't exist yet. It's a pretty damn cool library.

worked on the roadmap https://github.com/nim-lang/Nim/pull/19388 (enable -d:nimPreviewFloatRoundtrip and -d:nimPreviewDotLikeOps) and found that an important_packages (datamancer) failed. So I made a PR (https://github.com/SciNim/Datamancer/pull/23). It is not a bug of nimPreviewFloatRoundtrip(It seems like a precision problem to me) so alternatively datamancer can be disabled transiently.

There seems to be two major ones for Nim, NimData and Datamancer. Which one is better?

> Unfortunately there seems to be a big "civil war" happening right now in Nim land

I believe the war is already over, the other side forked the language and seems to move in their own direction to create something new - https://github.com/nim-works/nimskull . That's probably for the better.

I've been around Nim communtiy around a year and I haven't seen any major conflicts break out since these people left. Nim is still actively developed and a jou to use.

FYI, some members of the Nim community are working on a fork, for apparently similar reasons as OpenD (community-led development). https://github.com/nim-works/nimskull under active development and not ready for general consumption though, from my understanding.

There's a looming feeling that C++17 is really going to be the last version of C++ (practically, in production). The Vasa is now half-sunk [0][1], but the alternatives are yet to be truly born. The current issues surrounding the language standards:

- The important but half-baked features of C++20 that has never really been polished enough for actual production usage (modules, coroutines)

- Unnecessary "hyper-modern" C++ features which are dead on arrival (ranges)

- The dramatic increase in build times due to the STL library (which are accelerated by those hyper-modern C++ features) [2]

- The fleeing of LLVM/Clang engineers to other projects (as you've said, Apple engineers shifting work to Swift, and Google abandoning Clang and moving to Carbon).

- Implosions in the ISO committee (notably the controversy surrounding the rape convict)

It's really not looking good, but there aren't that much alternatives so I think people will just stick to C++17 for the moment. Listing the worthwhile competitors:

- Rust is a bit too awkward to use in many cases where C++ is used (particularly with unsafe Rust), and inherits some of the hyper-modern complexities/insanities of C++.

- Zig is still too unstable, they just finished reworking the compiler

- Jai is not even released to the public

- D might be a candidate but IMO they should really commit 100% fully for GC-less betterC mode...

- Nim still has many warts and unbaked features, and also the dev community was split into half recently [3]

[0] https://www.aristeia.com/TalkNotes/C++vstheVasa2-ups.pdf

[1] https://www.stroustrup.com/P0977-remember-the-vasa.pdf

[2] https://old.reddit.com/r/cpp/comments/o94gvz/what_happened_w...

[3] https://github.com/nim-works/nimskull

I started programming in Nim around 2015 and still write code in it from time to time. At this point I would have a tough time suggesting the language to anyone for much. While you can certainly accomplish almost any programming task with Nim, how much frustration you will encounter fighting the compiler and broken / under-specified language features and semantics might be a turn-off. There are other major warts with Nim, which I'll outline briefly below.

1) Nim's leadership is awful and has always been historically. Those in charge of managing the community are more interested in their personal reputation's and resumes than they are actually contributing working software to the language's ecosystem. Even the BDFL treats Nim like their own personal compiler R&D playground. There are so many broken features in Nim which never see the light of day or never get removed.

2) Continuing to expand on the point above, the Nim compiler has become insanely difficult to work on. As more and more half-baked features have been added to the language, the situation has only worsened. There are many would-be contributors who have come into the community only to leave completely frustrated or appalled by the lack of interest in improving the situation from those leading the community.

3) The development path is driven by leadership and not the community, and leadership has no plan. This was extremely evident last year when Araq and others were asked for a roadmap for Nim and they admitted to not having one, and basically wrote one up in a forum thread. Araq and dom96 and a few others, especially those who have been brave enough to actually deploy Nim code in production (looking at you status.im) tend to dictate what gets worked on or fixed. There is no coordination amongst folks working on initiatives. You can look at the `fusion` project, which was started by Nim's leadership, drew contributors in, and then was abandoned by leadership while maintainers were left on the hook to keep things afloat until they too dumped the project.

Things have gotten so bad, that a hard fork has been in development since last year, and many of the more senior community members or those who have been around for a bit have migrated there: https://github.com/nim-works/nimskull

Nim's community now consists of mostly new members or folks who weren't really active in it before, but maybe used Nim. Of course, the leadership remains in place, but there are only a handful of folks remaining that have been around for more than a year or two. Mostly those who bit the bullet on using Nim in production or built large projects with Nim and are stuck maintaining them.

My advice would be to look elsewhere.

A lot of previous contributors to Nim are currently working on an experimental fork due to disagreements with the development of the official compiler: https://github.com/nim-works/nimskull