3 ms·
Some 5-6 years ago I built a live streaming backend that used a custom C++ encoding front around Chromium on GPU servers on AWS. Mighty probably does something
by pavlov 4y ago
Some 5-6 years ago I built a live streaming backend that used a custom C++ encoding front around Chromium on GPU servers on AWS. Mighty probably does something pretty similar. It was the right solution for our users at that moment because our product was a professional tool at a relatively high price tag, and being able to run full HTML+CSS allowed us to deliver customized motion graphics quickly using available designer talent, so there was a distinct advantage there.
It was also quite expensive to run, and the stack was fickle because those Nvidia GPU servers aren’t designed to run client apps — they’re AI/ML solutions primarily. So I’m not surprised that Mighty is shutting down: the infra bills must have been running pretty hot and they seem to believe they can better spend their cash runway on AI, presumably on largely the same infra.
(Btw I’m giving a talk at the Kranky Geek virtual event on Thursday Nov 17 about cloud compositing which will discuss this Chromium adventure and what I believe is a better solution for most apps.)