Comment on Adobe tells you to use Chrome, not Firefox
phx@lemmy.ca 7 months agoHonestly, I kinda hate the idea of a browser being able to access hardware devices.
Comment on Adobe tells you to use Chrome, not Firefox
phx@lemmy.ca 7 months agoHonestly, I kinda hate the idea of a browser being able to access hardware devices.
ultratiem@lemmy.ca 7 months ago
That’s why no one outside Google wants. Apple said no. Firefox said no. There’s a reason. WebRTC is shit. It leaks too much just for a small convenience.
And yeah, browsers don’t need my USB ports thanks.
This move was what hurt VIA as they moved to the API exclusively. So the only native apps are just electron wrappers 🤷♂️
MonkderZweite@feddit.ch 7 months ago
At the end we have Flash + ActiveX alltogether again.
ilinamorato@lemmy.world 7 months ago
WebRTC and WebUSB are different things. RTC doesn’t provide direct port access, afaik.
ultratiem@lemmy.ca 7 months ago
Both are shit and developed by the same foundation. Browsers are not meant to negotiate its hardware. Period. This world will never be ready for that.
ilinamorato@lemmy.world 7 months ago
Have you worked with either before? They’re completely unrelated technologies, with similar names. They have nothing to do with one another. They’re not even being developed by the same groups. They emphatically do not have the same fundamental premise. I’ve built apps in WebRTC before, and I can guarantee it has nothing to do with WebUSB, and in fact with any sort of device-level hardware control.
To reiterate: the only connection between WebUSB and WebRTC is the fact that they’re named “Web” + three letter initialism.