Dmitry Ponyatov

For IoT applications Nim requires integration with newlib+FreeRTOS+FAT32+lwip for all embedded devices, and bare metal i386 (IoT platform over unikernel): threading, realtime task switching, lwip, minimal file system (maybe RAM-only...

For IoT server: embedded Linux or unikernel, message-passing distributed computing including load balancing and on-demand scalability, async Web server/interface with process control widgets, and math&ML plugins interface (for custom user...

End nodes require a DSP library for measurement processing and signal filtering.

Is Nim has some sort of (async) message passing? It can lead good parallelization both for generic low-core processors, and computing grids and NUMA systems.

Maybe this can be done in yield/generators implementation described here: http://yieldprolog.sourceforge.net/ I don't test it, maybe coroutines implements backtracking in a parallel can be tried as implementation base.

Maybe some effort should be done for extending the language with minimalistic coroutines and (async) message passing with very limited message sized especially for low-end microcontrollers (STM32L0 like). This method...

It would be great to have rich scripting facilities (Python?) to making more or less complex things in the running QUCS instance. At least, I want to use QUCS as...

Oops, I made issue using temporary account.

I make preview .pdf @ https://github.com/ponyatov/seco/releases/download/250517/Developer_250517.pdf Is 2.1.1-3 sections (github cloning) ok for subfork creation by newbie developer ?

Maybe scripthost part of Seco should be moved to HDGB level, so scripts can be evaluated in context of knowledge database. Or something like GUI -> scripthost -> HGDB chain.