(PS my humble opinion is "yes we should". I like being able to develop a heart rate monitor PWA for my phone, and I don't see what's different from granting some random native app the same access. At least with the web I can read the underlying code.)
It did absolutely nothing on my 2015 MacBook (tried Safari, Chrome and Firefox).
It does work on 2012 MacBook model on Google Chrome. I guess it only works on MacBook models that supported a mechanical disk — I think the sensor exists in the first place to protect spinning rust disks by parking the heads just before impact.
I just noticed that [4] doesn't work on Safari or Firefox either (but does on Chrome) on my MacBook 2010. Maybe it wasn't the best demo of that feature ...
The API is pretty well supported on tablets and phones though, which is where the main use case is.
It also works on your MacBook. [4]
[1] https://w3c.github.io/deviceorientation/
[2] https://caniuse.com/#feat=deviceorientation
[3] https://www.engadget.com/2010/07/06/google-chrome-gets-some-...
[4] https://simpl.info/deviceorientation/
(PS my humble opinion is "yes we should". I like being able to develop a heart rate monitor PWA for my phone, and I don't see what's different from granting some random native app the same access. At least with the web I can read the underlying code.)