How to generate e-waste
1) write an article about streaming an mjpeg, will generate e-waste locally
2) publish the article on Tom's Hardware, will generate e-waste on Tom's Hardware
3) wait for the innocent readers, will cause a domino effect causing a massive amount of e-waste in the form of internet traffic, data written in the backend of Tom's Hardware and data written on thr readers' machines
The sole purpose of this comment is to highlight how low the bar is for Tom's Hardware to publish articles... I will refrain on publicly speculate on why......
The code literally takes the pic from the cams encoded in JPEG and stream it giant JPEG as mjpeg (sequence of JPEGs), not even merging the streams in a large one or not even syncing the streams or discarding the outdated frames in case of sudden slowness.
Just to mention, he pi5 can easily generate H264 via software although it can be easily encoded in hardware.