No matter what you are using, they are always there, editable/hackable.
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.
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.
The written tone used in the repo comes of as too drastic, specially as it only reports the collection of analytics on how LinkedIn users use the website.
Is the detection result reported back to LinkedIn?
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?
"The linked posts dismiss this early because of the possibility to cause DDOS, but really, you can already do that from a hacked desktop "Quake", so there is no harm in being able to do it from a browser-based "Quake"."
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.
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.