That's certainly true to an extent. Other commenters have already highlighted necessary complexities. There is absolutely a lot of very entrenched "ways-of-working" that add unnecessary complexity, as with every domain. Not everything is a technical problem though and the social / process side of this sort of setup is what can make it work at all.
ST 2110-22 is codec agnostic. It just standardises CBR compression, for which JPEG-XS is a good fit today.
For plug-and-play IPMX (https://ipmx.io/about/) is looking to be a pretty promising approach that combines ST 2110 with NMOS, auth, encryption and other useful features. It's targetted at the ProAV market but IMO should be mostly suitable for consumer use.
Wish I was seeing more ST 2110 and IPMX open source work about. Would really love for good or at least common protocols to be broadly usable, available, via some good libraries.
I think the core caution is this is not type-level checks. Anything this validates still needs to be eval'd. It's not a guarantee of correctness for all inputs but does look to be a fairly light (and useful) tool to make unexpected states easier for you and others to identify.
I think they're saying that brutalist architecture feels out of context in Brisbane's weather, whereas the gloomy dreary feeling of the building fits in perfectly in the former USSR's gloom
You're entitled to that opinion, but if you give an alternative for how a big multi-storey building for large events and crowds should look then it will move the discussion forward.
If so, one benefit is you can quickly and safely mix up your set of agents (a la Inverse Conway Manoeuvre) without the downsides that normally entails (people being forced to move teams or change how they work).
reply