librespot VS wasmer

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

This is awesome. I'd love to have upstream support in Wasmer ( https://wasmer.io )

WebAssembly is extremely portable. WebAssembly runs on: all major web browsers, V8 runtimes like Node.js, and independent Wasm runtimes like Wasmtime, Lucet, and Wasmer.

Unfortunately cosmopolitan wouldn't work for dockerc. Cosmopolitan works as long as you only use it but container runtimes require additional features. Also containers contain arbitrary executables so not sure how that would work either...

As for WASM, this is already possible using container2wasm[0] and wasmer[1]'s ability to generate static binaries.

[0]: https://github.com/ktock/container2wasm

[1]: https://wasmer.io/

I could not find any guide how to add WASM container capability to Docker running on Colima. This guide provides a few Colima templates for exactly this, which adds WasmEdge, Wasmtime and Wasmer runtime types.

Just suggested as well Wasmer on Twitter! https://github.com/wasmerio/wasmer

Looking forward to seeing the results :)

The Biome team has been incredibly fast on solving the challenge and achieving 95% compatibility with Prettier [1]

Just as a note, as it was not mentioned in the article, Wasmer [2] also participated with a $2,500 bounty to compile Biome to WASIX [3], and it has been awesome to see how their team has been working to achieve this as well... hopefully we'll get Biome running in Wasmer soon!

Keep up the great work!!

[1] https://github.com/biomejs/biome/issues/720

[2] https://wasmer.io/

[3] https://wasix.org/

It's funny how WebAssembly can help overcome most of the issues mentioned on the blogpost (packaging, configuration, portability) if addressed properly.

That's the main reason Wasmer [1] was created :)

[1] https://wasmer.io

Thanks for the mention to Wasmer.

I'll put here a link in case is useful for future readers: https://wasmer.io/