We replaced H.264 streaming with JPEG screenshots (and it worked better)

Re:We replaced H.264 streaming with JPEG screenshots (and it... by ozim on Tuesday December 23, 2025 @06:39PM (#46370811)

*Why are we badly reinventing MJPEG instead of configuring the tools we already have?*

Getting to know and understand existing tools costs time/money. If it less expensive or more expensive than reinventing something badly is very complicated to judge and depends on loads of factors.

Might be that reinventing something badly - but good enough for the case is best use of resources.

[ Parent | on HN ]

Re:We replaced H.264 streaming with JPEG screenshots (and it... by antisol on Wednesday December 24, 2025 @02:02AM (#46373184)

From TFA:

    Implementation complexity: 
     h264 Stream: 3 months of rust
     JPEG Spam: fetch() in a loop

I don't see how it could have taken 3 months to read up on existing technologies. And that "3 month" number is before we start factoring in time spent on:

* Writing code for JPEG Spam / "fetch() in a loop" method

* Mechanisms to switch between h264 / jpeg modes

* Debugging implementation of 2 modes

* Debugging switching back and forth between the 2 modes

* Maintenance of 2 modes into the future

[ Parent | on HN ]