Parallel-And-Concurrent-Programming VS areg-sdk

I've explored concurrency in C++, Python, and Node.js, and kept notes and examples in a repository. I think it could be helpful to others, so I'm sharing it here: https://github.com/djeada/Parallel-And-Concurrent-Programming

Long time I was not here and I am very sure that none missed me :) I was busy developing new features of areg skd and creating user interface tool for areg sdk. And I must say, that working almost alone for more these 2 project, I made a huge progress. And what is very important, I have fun.

FP Libraries: gRPC, ZeroMQ, and AREG are examples of libraries with a special focus on providing possibilities for Interprocess Communication. Developed using C++, they facilitate communication through predefined APIs, emphasizing functional programming concepts.

In addition, if the owners of the repositories add more relevant and precise labels to the issues, it increases the possibility that the OSS developers find the issues they would loved to resolve. For example, the issues of AREG SDK which marked "help wanted" in addition have such labels like "C++" or "cmake", "unit test", etc.

My closer introduction with these 2 tools started from OSS areg sdk project. Because of some experienced friend recommendation, i started with make. The main reason was that it is more spread in embedded. No other weighty argument they had. After having make, i decided to integrate cmake. Suddenly i figured out that cmake for me is more understandable and powerful. It already has many features that makes things easier. The biggest advantage for me is that in comparison to make / Makefile, lot of IDE support build with cmake. The cross-platform / cross-compile for areg-sdk is important feature, and this is easier to achieve with cmake. For example, I can compile with make under Linux with gcc/clang, but under windows can compile in cygwin environment and not with MSVC, which is not the issue in case of cmake.

Project: AREG is a cross-platform interface-centric lightweight communication engine, which forms a grid of services in the IoT fog- and mist-network, automates the real-time transmission of data between multiple connected software nodes, so that the connected Things interact like a thin distributed servers and clients. Technologies: C/C++17, standard library dependencies, POSIX and Win32 API. Can be used in real product.

Nice. I also have own project, but it already requires much time, so that cannot join in other projects. As well, up to now have no dependencies, except standard system libraries. I think, we should have a separate post to share projects and give short description. Some might be interested to join.