pheres
However I would argue that it makes it slightly harder to make any change. You no longer have a single class with all the styles that are affecting that element.
You can change the classes in the harder to read html, or override the single element. There is no longer the possibility to, for example, affect all .primary-btns.
Only when you become replaceable at a certain task (or able to delegate it) you can progress to do new (more interesting) things.
Everyone's experience differs quite a bit depending on the used client library (plain, apollo or relay) or the server library specific for your server languages.
Is the detection result reported back to LinkedIn?
In their [Privacy Policy](https://www.linkedin.com/legal/privacy-policy#your_device_an...) they do mention they collect information on "web browser and add-ons".
This reminds me of similar approaches used in other environments. For example in the game industry, anti-cheat techniques of detecting the running software in mobile devices to flag users. How do you think this differs?
No same-origin-policy would be lovely combined with XSS vulnerabilities.
Suddenly all the visitors of that website would be doing DDOS on a random host.
Todays netbooks are too limited to even deserve a screen bigger than 10" and I guess the main purpose of a netbook is to be small and portable.