Hacker News new | ask | show | jobs
by gkop 2080 days ago
I’m struggling to understand your point. Phones are closer to laptops in that in typical use a wired power connection is frequently plugged and unplugged, so mechanical wear is an important consideration. Why are you bringing up Ethernet on servers in this context, when as you say the pattern of use is utterly different?

I know almost nothing about wireless charging. But have fair experience with working with WiFi devices. In my lifetime, I have observed 0 cases of failure on the WiFi client mechanism, and exactly 1 case of a WiFi router failing due to hardware. Meanwhile, power plugs are the most common part I have experienced wearing out on consumer electronics. Have you experienced lots of failures of solid state electronics due to eg. hear cycling and magnetic fields?

1 comments

My point was you need to design stuff for the use case and a healthy margin. Incandescent lightbulbs are perhaps the poster child for solid state devices which with a limited lifespan. You can design lightbulbs for a 100 year lifespan at the cost of efficiency and bulb brightness. Even then an incandescent bulbs lifespan is dramatically shorter if your power cycling it every 2 minutes. But eventually stuff like electromigration for example will be an issue for solid state devices. https://en.wikipedia.org/wiki/Electromigration

When designing wireless charging the same efficiency vs lifespan tradeoffs exist. Sure, they might be fine, but don’t expect them to last 20 years or anything. Further, the mats are significantly more expensive than a cable.

PS: Connector specifications are generally a dumpster fire because nobody wants to be forced to build expensive cables. And even if the spec says X, if Y is cheaper and still mostly works then you can bet people will do Y. Failure tends take a while at which point people buy a new cable vs returning the old one etc.

Thanks! Your answer reinforces my personal preference for wires to supply power :)