snowfs VS libuv

Have you heard of https://www.snowtrack.io? It’s like a GitHub fork based backup system for any folder. I haven’t tested it much but the dev is active on Reddit and was looking for people to test it not too long ago

I'm looking for a program like git and GitHub for large files, (like Blender/Krita/etc... files). I already found some stuff like Snow Track, Alien Brain, but I want something free and with cloud storage to share my work.

I was actually testing Snowtrack recently, worked pretty good so far, especially since it is built around working with 3D files.

Generally speaking, Git and PlasticSCM are both great candidates, although they both require some technical background. We are working on an open-source version control system called SnowFS for graphic projects.

I've used ShareIO in the past along w/ Google Drive or Dropbox. It works well, but has some limitations. There are also these version control apps. Currently in beta. https://www.snowtrack.io https://www.anchorpoint.app

It's very interesting to see how many industries are behind version control and that it never got picked up in big style. Exciting times ahead! :-) Btw, you can see the end-result at www.snowtrack.io

We are looking for contributors who can help with their expertise to make an official npm package out of SnowFS. If you're interested to join, feel free to check out this new issue

I'm a maintainer of a project called SnowFS. SnowFS is a high-performance command-line application and node library for Windows, macOS and Linux with a focus on binary file versioning, written in TypeScript.

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.