you are viewing a single comment's thread
view the rest of the comments
[–] 65 points 1 month ago (19 children)

All of these wed based uber-projects are built on Chrome. This is bad. This gives more control to google and strengthens their strangle hold over web technologies.

  • source
  • hideshow 19 child comments
  • [–] 55 points 1 month ago (6 children)

    It's also bad because why the fuck should a web browser have that much access to the hardware to begin with?!

  • source
  • parent
  • hideshow 6 child comments
  • [–] 15 points 1 month ago (3 children)

    Considering they made Chrome an entire OS... It was sort of necessary for that and probably minimal to bring it to the regular desktop browser.

    Otherwise it doesn't really need to, other than simplicity for the end user. Being able to just go to the website regardless of platform and not having to install anything, or keep anything up to date, is a nice end user experience.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 14 points 1 month ago*

    Considering they made Chrome an entire OS… It was sort of necessary for that and probably minimal to bring it to the regular desktop browser.

    That's both plausible and insightful on your part. Thanks!

    That said, just because they could easily do it on the non-ChromeOS version of the browser doesn't mean they should have.

  • source
  • parent
  • [–] 20 points 1 month ago* (4 children)

    Cause WebUSB still only exists on Chrome, even though Mozilla and Apple had 9 years to catch up: https://developer.mozilla.org/en-US/docs/Web/API/WebUSB_API#browser_compatibility

  • source
  • parent
  • hideshow 4 child comments
  • [–] 17 points 1 month ago (3 children)

    "to catch up", while they deliberately choose not to implement this. they don't just not do it, they outlined why.

  • source
  • parent
  • hideshow 3 child comments
  • [+] -6 points 1 month ago (2 children)

    their competitor has an advantage and real leverage, I'd say that's enough reason in economics? I get why it isn't implemented, but all that means is that chromium has the high ground when it comes to this.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 month ago (2 children)

    Maybe some of the other browsers should implement the tech needed to do this kind of thing then? Cause as far as I know, Chrome is the only browser that can give a websites access to USB.

  • source
  • parent
  • hideshow 2 child comments
  • [+] -9 points 1 month ago (3 children)

    Jesus fucking christ can't you people ever just let something be good for once

  • source
  • parent
  • hideshow 3 child comments
  • [–] 22 points 1 month ago (2 children)

    Adding security, compatability, and vendor lock-in issues in exchange for convenience is not a good thing. Remember ActiveX and Silverlight? They forced users into uning IE. I am still finding industrial applications whos only config page is some ancient, IE only, nightmare.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 1 month ago

    In this case the spec is published, so it wouldn't be a lock-in or compatibility issue if the other vendors didn't lock themselves out.

    Security, I get, but when I've used it to flash esp32s before the user agent pops up a box asking me which device I want to give access to before the website sees anything, so it's not transparent and it doesn't give it access to everything on my system.

    I use Firefox all the time, but keep a Chromium on my system basically for stuff like this occasionally, and also web calls because Firefox's implementation of the audio API doesn't let me change microphones in the webapp, it just exposes one mic, and I've had issues with that before, so I join all calls in Chromium.

  • source
  • parent