3 ms·
Good to see the pivot before cash ran out, but sad news :( Good luck to the team! IMO Mighty is too early bc they didn't tackle the SW side, 'just' the remote
by lmeyerov 4y ago
Good to see the pivot before cash ran out, but sad news :( Good luck to the team!
IMO Mighty is too early bc they didn't tackle the SW side, 'just' the remote nature, so couldn't get their 10X. The 10-100X shift today comes from apps running differently on cloud resources, not just lift-and-shift. That already exists as the VDI market.
Ex: We do client GPU <> cloud multi-GPU for cyber/fraud/etc analysts wanting to visually investigate how their many events stitch together, and Otoy does same for movie effects. In the consumer market, seeing same rewrites in say gaming. In a sense, Mighty's pivot to generative AI is the same -- faster to use remote multi-GPU services.. but custom built accelerated visual app for 100Xs, not lift-and-shift.
Without tackling the SW rewrite problem, hard for Mighty to get these wins via a lift-and-shift :( I do think federating cloud resources so users can bring their own and devs can reliably tap them would be amazing, but we seem still in the dev-controlled-server era. As someone trying to build predictable 100X experiences, that feels likely for awhile. Such a shift could have been webgl2 etc standards enabling modern multigpu apps in the browser... but Google and Apple web GPU browser/standards leadership have long strangled that path.
In a related note, we are starting to launch our global GPU edge network, and looking for a backend/infra eng on that + related AI services build out -- Nodejs/python/k8s. We are profitably growing: I agreed with Mighty's pattern before it even existed (my PhD at Berkeley explored it!), just easier ROI right now by sticking at the app layer.