4 ms·
I imagine this is for video site's that still have a lot of flv's which they'll never reencode but want to work on devices that don't have flash player.
by bobajeff 10y ago
I imagine this is for video site's that still have a lot of flv's which they'll never reencode but want to work on devices that don't have flash player.
- exodust 10y agoMaybe, but then again it says "long live FLV!" on the github page, as if they actually favor this format.
- qb45 10y agoI think it might possibly be sarcams ;)
- davidcollantes 10y agoIt is. :-)
- cooper12 10y agoIt's a play on the phrase "The king is dead, long live the king!", which means long live the successor, who is flv.js in this case.
- exodust 10y agoYes I understand the origin of the phrase. To keep running with your great story about the king, it is not the JS library which is the successor, as you claim, it's still FLV. Which brings us back to the original question of why this was done in the first place - the reason now I don't even care to know.
- cooper12 10y agoI assumed it was done for historic reasons so in the future websites like archive.org could continue playing flash. (like Shumway [0]) We would lose a huge library of videos that were created in the format if we could no longer play them due to browser policies and the obsolescence of the format. In terms of video encoding, there are much better options these days that don't involve transmuxing from flash when you're already encoding in h.264, so it likely isn't so sites can continue serving Flash. [0]: https://github.com/mozilla/shumway https://github.com/mozilla/shumway