3 ms·

I don't understand where you see complexity here. That was a fairly simple setup actually. About the use cases and motivations, some of the drivers were commer

by myth2018 5y ago

I don't understand where you see complexity here. That was a fairly simple setup actually. About the use cases and motivations, some of the drivers were commercial -- e.g. clients with content they considered too sensitive to be hosted off-premises; clients distributing content to places with limited connectivity; also, integration with custom access control systems. The list goes on.

technobabbler 5y ago
> I could do pretty much everything I needed using ffmpeg (compiled with a customized configuration), video.js running a handful of custom plugins and some other pieces of open source software. This. That's so many points separate points of failure, and doesn't that mean you have to get a dev involved (or have an in-house automated video pipeline) anytime someone wants to post or update a video? Maybe we just have different thresholds of "complexity". I try to keep clients away from unnecessarily bespoke tools, and keep them on simple GUIs supported by proper vendors... but that's just in my sphere of work. In bigger teams it might make sense to in-house more stuff.