That's a start at improving something. But it won't rid itself of the Playskool/Fisher-Price gimmick factor or have any lasting effect until we can convince JS developers to write their own tools in a standards-compliant dialect and use standardized APIs so that contributors can use the runtime they already have installed instead of being cajoled and browbeaten into installing NodeJS or Bun or Deno or whatever to do…
Build Adafruit projects right from Firefox
11–20 of 96 posts
Re: Build Adafruit projects right from Firefox
#12WebSerial was just introduced in Firefox 151. It was already available for 5 years in Chromium based browser. It's so new in Firefox that even caniuse is not up-to-date: https://caniuse.com/web-serial .
Re: Build Adafruit projects right from Firefox
#13Re: Build Adafruit projects right from Firefox
#14Re: Build Adafruit projects right from Firefox
#15I've always agreed with the reservations about browsers being able to control peripherals. I'd rather download a python script i can inspect.
Re: Build Adafruit projects right from Firefox
#16WebSerial was just introduced in Firefox 151. It was already available for 5 years in Chromium based browser. It's so new in Firefox that even caniuse is not up-to-date: https://caniuse.com/web-serial .
interestingly, MDN web docs claims at the top of the Web Serial page ( https://developer.mozilla.org/en-US/docs/Web/API/Web_Serial_... ) that Chrome does not support it, even though the support table at the bottom shows that it supports all of the features (Firefox doesn't) and has for longer than Firefox
Re: Build Adafruit projects right from Firefox
#17Re: Build Adafruit projects right from Firefox
#18Re: Build Adafruit projects right from Firefox
#19On iOS the page promotes the App Store version of Firefox, which is based on WebKit and doesn’t support Web Serial.
Re: Build Adafruit projects right from Firefox
#20> For raw device access as envisioned in a number of APIs (Web USB, Web Bluetooth, Web NFC, and Web MIDI), the risks of exposing those APIs to users cannot be reasonably conveyed. This is pretty much an intractable flaw of allowing raw, non-semantic access to devices regardless of the protocol used to do so.
> The specific issue is: it's not intuitive that allowing malicious-site.com to access your Bluetooth keyboard might give that site access to your stored passwords, give them the ability to hijack your DNS settings, or allow them to encrypt your hard drive and hold it ransom. And if it's not immediately obvious how those things are possible, that only serves to demonstrate how completely non-intuitive the risks are and how intractable trying to explain them in a permission prompt would be.
https://github.com/mozilla/standards-positions/issues/95#iss...