Hardware
A community for news and discussion about the hardware side of technology. Questions and support posts are also welcome, so long as they are relevant to hardware and interesting technologies therein.
Rules
1. English only
Title and associated content has to be in English.
2. Use original link
Post URL should be the original link to the article (even if paywalled) and archived copies left in the body. It allows avoiding duplicate posts when cross-posting.
3. Respectful communication
All communication has to be respectful of differing opinions, viewpoints, and experiences.
4. Inclusivity
Everyone is welcome here regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
5. Ad hominem attacks
Any kind of personal attacks are expressly forbidden. If you can't argue your position without attacking a person's character, you already lost the argument.
6. Off-topic tangents
Stay on topic. Keep it relevant.
view the rest of the comments
I try to click on something and it doesn't react.
Is this because I failed to execute the click (has happened, especially on laptop touchpads), or because the site is unresponsive/buggy?
As a person not too familiar with hardware or what goes into mouse creation, I have always taken the "click" sound as something that can only happen when I actually successfully execute the click. That I made those two connectors touch. (Of course, the OS might drop it and the software part does not work, but I do take it as I made all the physical things that need to happen to make a click happen.) So if I get to hear the "click" on a mouse I know for sure if I clicked or not, if it's human error or not in the problem I posed. If I don't I'm going to be clicking a lot more times to ensure I got a real click through, because I am not sure if I actually managed to click.