3 ms·
OK there's a bunch of jellyfin clients tho. This is an Apple Music client. why you gotta drag somebody over this.
by jazzyjackson 1y ago
OK there's a bunch of jellyfin clients tho. This is an Apple Music client. why you gotta drag somebody over this.
- MangoToupe 1y agoWhy does it matter what the backend is? A music player is a music player; it shouldn't matter where the music comes from.
- slau 1y agoWell, it matters when you have to integrate with APIs and idiosyncrasies of third parties, and whatever draconian DRM they require. It’s obviously not impossible to add support for multiple backends, but from a development effort it definitely matters. It’s not like streaming platforms are gingerly implementing open and common standards for music streaming. Winamp had support for .m3u and streaming back in ‘04, but we’ve moved on from that.
- MangoToupe 1y agoSure, but presumably that is different from the actual value of the app itself—the frontend. It's just a matter of effort to connect the interface to the backend. Why you'd insist on tying the two together is anyone's guess (likely convenience).
- jazzyjackson 1y ago> (likely convenience). AKA the limited resource of developer-hours
- MangoToupe 1y ago> AKA the limited resource of developer-hours Sure, but each connected backend magnifies value to end-user. To say any one client is worth devoting to just a single backend is crazy.
- connorgurney 1y agoBut they never marketed it as a generic music player, did they? It also isn’t a toaster.
- MangoToupe 1y ago> But they never marketed it as a generic music player, did they? It also isn’t a toaster. A music player is very much a dumb pipe (or "toaster" as you call it). There's nothing special about Apple Music that makes it a backend worth devoting an entire client to.
- connorgurney 1y agoThat’s your opinion though, is it not? To OP, Apple Music might be the world and then some.