I'm not sure about that and if it is so, it's very recent. Playing online isn't bad and addictive per say I would argue though.
My comment was more in response to someone who seemed to associate chess to the main online platform which to me, is using addictive patterns to some level.
You might also want to mention AMWA NMOS, which is increasingly used alongside SMPTE 2110 in setups like this. NMOS (Networked Media Open Specifications) defines open, vendor-neutral APIs for device discovery, registration, connection management, and control of IP media systems. In practice, it's what lets 2110 devices automatically find each other, advertise their streams, and be connected or reconfigured via software.
The specs are fully open source and developed in the open, with reference implementations available on GitHub (https://github.com/AMWA-TV)
The specs define REST API's, JSON schemas, certificate provisioning, and service discovery mechanisms (DNS-SD / mDNS), providing an open control framework for IP-based media systems.
Hi! I have been happily using Ardour as a hobbyist since version 5. At the same time I also started learning Pure Data. I was wondering how difficult it would be to implement a feature similar to "The Grid" from Bitwig. I’m not sure whether this could be done as a simple plugin, or if it would require much deeper integration with Ardour.
Joking aside, I often hear people say "they should" when talking about GNU/Linux (for example: "they should just standardize on one audio stack"), as if there were a central authority making those decisions. What many don't realize is that with FOSS comes freedom of choice... and inevitably, an abundance of choice. That diversity isn't a flaw, it's a consequence of how the ecosystem works.
That is very true. But because it is open source, one can request for packaging, contribute a package, use a third-party repository, or build it from source when needed.
For distro-packaged FOSS, binary compatibility isn't really a problem. Distributions like Debian already resolve dependencies by building from source and keeping a coherent set of libraries. Security fixes and updates propagate naturally.
Binary compatibility solutions mostly target cases where rebuilding isn't possible, typically closed source software.
Freezing and bundling software dependencies ultimately creates dependency hell rather than avoiding it.
Paying makes sense when you actually need/use those services. Paying "because you can" feels wrong to me. If the goal is to support FOSS, there are many more ways to contribute than subscribing to a service you don't use.