4 ms·

> I'm not really seeing Chrome suffering from privacy problems coming from MIDI devices. Here's a CCS paper detailing why it's a bad idea for browsers to expos

> I'm not really seeing Chrome suffering from privacy problems coming from MIDI devices. Here's a CCS paper detailing why it's a bad idea for browsers to expose HW details without careful consideration: https://www.cs.princeton.edu/~arvindn/publications/OpenWPM_1_million_site_tracking_measurement.pdf https://www.cs.princeton.edu/~arvindn/publications/OpenWPM_1... > if you aren't into making music or learning keyboard or what have you, I guess you wouldn't care about MIDI Considering the aforementioned problems, why would it make sense for browsers to prioritize MIDI above all else? And I highly doubt your six year old would refuse to use native apps, given the chance. > (native apps) are often a bigger threat I choose my native apps with care. For many apps, moving to the web doesn't mean that I would have to stop caring about trust. It just means that I would have to start being more careful about which sites I visit if browsers keep on exposing random HW details. > need to be made for each platform If you're only supporting Chrome, then you've stopped caring about portability. You're making it the user's fault if they don't use Chrome.

robbrown451 6y ago
"why would it make sense for browsers to prioritize MIDI above all else?" Who said above all else? That's pretty black and white. You could make the same argument if Firefox didn't support, say, microphone or camera. If you don't happen to use them (say, you don't use video chat as many didn't prior to 2020), you could ask why they are so important. It's just one thing that Chromium does (and has done for year), that Firefox doesn't. >And I highly doubt your six year old would refuse to use native apps, given the chance. Which native app? The one she uses only works in a browser, and wouldn't work natively because it uses other things a native app can't use (such as YouTube interaction/synchronization). Also the graphics are far superior to anything I've seen not done in a browser, because it taps into other things that would be immensely difficult if the browser didn't make them available at a pretty high level. https://youtu.be/64PkqQuE9h8 https://youtu.be/64PkqQuE9h8 https://www.youtube.com/watch?v=NV6rdmdZnkA https://www.youtube.com/watch?v=NV6rdmdZnkA And that app works on her Chromebook, as well as on my Windows and Mac machines. I get that you like Firefox, but I don't see "you can just do that with a native app" as a great advertisement for it.

robbrown451 6y ago

"why would it make sense for browsers to prioritize MIDI above all else?" Who said above all else? That's pretty black and white. You could make the same argument if Firefox didn't support, say, microphone or camera. If you don't happen to use them (say, you don't use video chat as many didn't prior to 2020), you could ask why they are so important. It's just one thing that Chromium does (and has done for year), that Firefox doesn't. >And I highly doubt your six year old would refuse to use native apps, given the chance. Which native app? The one she uses only works in a browser, and wouldn't work natively because it uses other things a native app can't use (such as YouTube interaction/synchronization). Also the graphics are far superior to anything I've seen not done in a browser, because it taps into other things that would be immensely difficult if the browser didn't make them available at a pretty high level. https://youtu.be/64PkqQuE9h8 https://youtu.be/64PkqQuE9h8 https://www.youtube.com/watch?v=NV6rdmdZnkA https://www.youtube.com/watch?v=NV6rdmdZnkA And that app works on her Chromebook, as well as on my Windows and Mac machines. I get that you like Firefox, but I don't see "you can just do that with a native app" as a great advertisement for it.