4 ms·
You can set up red5 in a few minutes, at most hours. Replicating a similar setup with something like Janus is a lot more complicated, and there is no HTML5 equi
by buboard 7y ago
You can set up red5 in a few minutes, at most hours. Replicating a similar setup with something like Janus is a lot more complicated, and there is no HTML5 equivalent
Plus webrtc is proving to be a resource hog every time, and a lot more complicated to set up in an app (separate media / data stream etc). flash/red5 works literally out of the package.
- cookie_monsta 7y agoI'm not asking what webRTC does worse - obviously it's going to improve over time, I'm asking what it can't do that flash can.
- buboard 7y agothat misses the point. If its slow and laggy, user is not going to use it and laptops are going to become portable heaters. This is exactly what webRTC does > obviously it's going to improve over time When? webrtc is like 10 years old. How long we have to wait to go back to 1999?
- cookie_monsta 7y ago> When? webrtc is like 10 years old. Well, 8 from initial release. 18 months from first stable release. Far as I understand it, lag and overheating are hardware/network problems. Considering the amount of development going into both of them, that situation is only going to improve but of course I don't have a roadmap. FWIW I haven't noticed problems with either and I don't have a mind blowing setup. I look at what browsers are doing now compared to 1999, there's no way I'd want to go back