librespot VS libuv

It is shitty they killed libspotify, but it isn't hard to reverse engineer the way the app communicates with the backend, this has already happened in the form of https://github.com/librespot-org/librespot as an example.

And if Apples ecosystem wasn't so locked down I could write a HomePod client using librespot and Daniel Ek could get however mad he wants about it.

https://github.com/librespot-org/librespot - it exists already. I'd just like to make it usable on a flip phone.

They use a version of this.

You want SnapCast. You'd run snapserver on your Linux box and snapclient on your Pi's. Snapserver has support for Airplay (via shairport-sync) and Spotify (via librespot). I recommend using MPD for your music library, as I don't think PlexAmp can output audio in a way that's useful for snapserver.

For the last tow days I'm trying to compile librespot for my Xiaomi Mop PRO STYJ02YM Vacuum Cleaner. Vacuum uses TinaLinux which uses OpenWRT under the hood. The platform is armv7.

Also, the base library doing the hard work of communicating with the proprietary Spotify service is still very healthy, since April 2015. I would say that is a pretty decent time no?

To replace it, I've purchased in-ceiling speakers and a Control 4 Amp (C4-16AMP3-B) which I can control via the network. I plan on using shareport-sync for AirPlay and librespot for spotify as the sources to play music. 90% of the use for my whole home audio is for music.

But, if I can control librespot, https://github.com/librespot-org/librespot that's interesting

You can also just use librespot, which acts as a Spotify Connect device so you can play music in your PC and control it from your phone in a very light way

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.