activepieces VS libuv

Activepieces - Build automation flows to connect several apps together in your app's backend. For example, send a Slack message or add a Google Sheet row when an event fires in your app. Free up to 5,000 tasks per month.

As per its description on github: N8n is a Free and source-available fair-code licensed workflow automation tool.

Not really OSS.

Check out: https://www.activepieces.com/

MIT open source.

There's also https://github.com/windmill-labs/windmill and https://github.com/activepieces/activepieces depending on which parts of retool and tooljet you care about.

I wonder how cptn compares with ActivePieces. AP's been declared the "Open Source Zapier" and I have been having a blast with it.

https://www.activepieces.com/pieces

https://github.com/activepieces/activepieces

There is an issue about this on our GitHub, you can comment on it with your specific use case to give it a push up, our piece building roadmap changes upon demand from users: https://github.com/activepieces/activepieces/issues/670

I use n8n to handle simple automations like this - and currently testing Activepieces too.

It was requested by someone, I'll appreciate it if you put some emphasis on the GitHub issue here: https://github.com/activepieces/activepieces/issues/438

I wound up on a different team with pre-existing Python code so temporarily shelved my use of Go for a bit, and we used Sanic (an async Python framework built on top of the excellent uvloop & libuv that also powers Node.js) to build some APIs for live channel management & operations. We hand-wrote our OpenAPI and used it to generate documentation and a CLI, which was an improvement over what was there (or not) before. Other teams used the OpenAPI document to generate SDKs to interact with our service.

In the source code of the Node.js opensource project, lib folder contains JavaScript code, mostly wrappers over C++ and function definitions. On the contrary, src folder contains C++ implementations of the functions, which pulls dependencies from the V8 project, the libuv project, the zlib project, the llhttp project, and many more - which are all placed at the deps folder.

Libuv, the C library that gives Node.js its asynchronous, non-blocking I/O capability is responsible for managing the thread pool. Node.js gives you the capability of using additional threads for computationally expensive and long-lasting operations to avoid blocking the event loop.

Node.js is written in C, C++, and JavaScript. The core components of Node.js - the V8 engine and the libuv library - are written in C++ and C, respectively, since these languages provide low-level access to system resources, making them well-suited for building high-performance and efficient applications. JavaScript is mainly used to write the application logic.

x8 apparently https://github.com/libuv/libuv/pull/3952

Notably upgrades to libuv 1.45 which has io_uring support. Faster file system access! Awhh yeah, it's on.

Remarkable what a mild & unintrusive PR adding io_uring was. https://github.com/libuv/libuv/pull/3952

Well, the single-threaded nature ultimately leads to its biggest downfall. Node.js utilizes a synchronous event loop engineered using Libuv that takes in code from the call stack and executes it.