4 ms·

Chromium is in the business of adding things websites should have no business concerning themselves with, like Bluetooth support, while removing support for use

Chromium is in the business of adding things websites should have no business concerning themselves with, like Bluetooth support, while removing support for useful things: now JPEG XL, previously RSS, MathML.

dieulot 4y ago
MathML is making a return next month. https://chromestatus.com/roadmap https://chromestatus.com/roadmap
- lol768 4y ago
  > MathML is making a return next month Yeah, and that's arguably thanks to Igalia and all of their sponsors. They've put a colossal amount of work into this project. If you have the means, it's worth donating for ongoing support, too: https://opencollective.com/mathml-core-support https://opencollective.com/mathml-core-support Google just removed it and would've been content with it staying gone. They said "it wouldn’t have been a good return on investment for us to do it".
thehappypm 4y ago
If JPEG XL was actually utilised they would not be deprecating it
- yakubin 4y ago
  How would a web developer use a feature, which is disabled by default? Should they put up a banner saying "in order to view this page, restart your browser with this command line parameter"?
  - lopkeny12ko 4y ago
    You'd use it the same way any other web feature without widespread browser support is rolled out--progressive enhancement, i.e. load it at runtime if heuristics indicate the necessary browser APIs are available, otherwise fall back to a "degraded" version.
    - tuxone 4y ago
      Not the parent commenter, though one thing is to support a feature that is somehow spread across some browser families and/or versions and another thing is to support a feature that is mostly unavailable on clients. It is probably not worth it form an economical point of view once you factor in the time spent developing/maintaining the feature plus (for this case) the additional required storage.
    - toastal 4y ago
      I use it with the picture element as the preferred codec. I found often AVIF was a bigger size than WebP and JXL so I stopped bothering as the encoding times are just awful.
- fuu_dev 4y ago
  I think the bug tracker around jpegXL support showed high interest and support for it already². Having it opt-in also does means most websites can't use it given that the vast majority of their userbase are on default settings. 2: https://bugs.chromium.org/p/chromium/issues/detail?id=1178058#c79 https://bugs.chromium.org/p/chromium/issues/detail?id=117805...
somrand0 4y ago
chromium is a business? I thought the business was Chrome, whereas Chromium was the open source (and GPLed) project that makes the code that Chrome uses and that would almost certainly not start out as GPLed if it was a new project now.
- charcircuit 4y ago
  Chrome isn't GPL.
  - somrand0 4y ago
    ah, so the open code would (will?) vanish the instant it's not cheaper (and-or better) to develop the core engine in this way.
deleted 4y ago
[deleted]
_flux 4y ago
Well MIDI support is pretty cool, I could just go to Novation website and update SL49 firmware (after appropriate confirmation). Also Tasmota project has a firmware upload over serial, pretty accessible if you have Chrome. I think Bluetooth could similarly be useful for e.g. heart rate monitoring apps for sports.
- tuxone 4y ago
  > I think Bluetooth could similarly be useful for e.g. heart rate monitoring apps for sports. As the op commented, why not leaving the burden of managing/pairing the heart rate monitoring device to the OS? In the same way audio and input devices work? The only real use case that comes to my mind with Bluetooth support is indeed monitoring, but it’s not about heart rate.
  - _flux 4y ago
    Because then you are limited by the use cases the browser vendors have thought of, instead of enabling new applications someone else thought of. I mean, why not also use it for controlling a LEGO robot from a Scratch app? Configuring presets of your coffee maker without needing a mobile app? Updating the firmware of your soldering iron via vendor web page? Just providing supervised access to Bluetooth LE would satisfy these all without adding custom interface for all current and all future devices we might want a web page to interact with.

dieulot 4y ago

MathML is making a return next month. https://chromestatus.com/roadmap https://chromestatus.com/roadmap

lol768 4y ago
> MathML is making a return next month Yeah, and that's arguably thanks to Igalia and all of their sponsors. They've put a colossal amount of work into this project. If you have the means, it's worth donating for ongoing support, too: https://opencollective.com/mathml-core-support https://opencollective.com/mathml-core-support Google just removed it and would've been content with it staying gone. They said "it wouldn’t have been a good return on investment for us to do it".

thehappypm 4y ago

If JPEG XL was actually utilised they would not be deprecating it

yakubin 4y ago
How would a web developer use a feature, which is disabled by default? Should they put up a banner saying "in order to view this page, restart your browser with this command line parameter"?
- lopkeny12ko 4y ago
  You'd use it the same way any other web feature without widespread browser support is rolled out--progressive enhancement, i.e. load it at runtime if heuristics indicate the necessary browser APIs are available, otherwise fall back to a "degraded" version.
  - tuxone 4y ago
    Not the parent commenter, though one thing is to support a feature that is somehow spread across some browser families and/or versions and another thing is to support a feature that is mostly unavailable on clients. It is probably not worth it form an economical point of view once you factor in the time spent developing/maintaining the feature plus (for this case) the additional required storage.
  - toastal 4y ago
    I use it with the picture element as the preferred codec. I found often AVIF was a bigger size than WebP and JXL so I stopped bothering as the encoding times are just awful.
fuu_dev 4y ago
I think the bug tracker around jpegXL support showed high interest and support for it already². Having it opt-in also does means most websites can't use it given that the vast majority of their userbase are on default settings. 2: https://bugs.chromium.org/p/chromium/issues/detail?id=1178058#c79 https://bugs.chromium.org/p/chromium/issues/detail?id=117805...

somrand0 4y ago

chromium is a business? I thought the business was Chrome, whereas Chromium was the open source (and GPLed) project that makes the code that Chrome uses and that would almost certainly not start out as GPLed if it was a new project now.

charcircuit 4y ago
Chrome isn't GPL.
- somrand0 4y ago
  ah, so the open code would (will?) vanish the instant it's not cheaper (and-or better) to develop the core engine in this way.

deleted 4y ago

[deleted]

_flux 4y ago

Well MIDI support is pretty cool, I could just go to Novation website and update SL49 firmware (after appropriate confirmation). Also Tasmota project has a firmware upload over serial, pretty accessible if you have Chrome. I think Bluetooth could similarly be useful for e.g. heart rate monitoring apps for sports.

tuxone 4y ago
> I think Bluetooth could similarly be useful for e.g. heart rate monitoring apps for sports. As the op commented, why not leaving the burden of managing/pairing the heart rate monitoring device to the OS? In the same way audio and input devices work? The only real use case that comes to my mind with Bluetooth support is indeed monitoring, but it’s not about heart rate.
- _flux 4y ago
  Because then you are limited by the use cases the browser vendors have thought of, instead of enabling new applications someone else thought of. I mean, why not also use it for controlling a LEGO robot from a Scratch app? Configuring presets of your coffee maker without needing a mobile app? Updating the firmware of your soldering iron via vendor web page? Just providing supervised access to Bluetooth LE would satisfy these all without adding custom interface for all current and all future devices we might want a web page to interact with.