Hacker News new | past | comments | ask | show | jobs | submit login

I mean, who the hell has a Cat-5e drop behind their fridge, though?

I imagine a product manager took exactly 100ms to calculate that the answer to that question is "functionally no one" and so there went the $X ethernet connector from the build, for patently obvious reasons.

Hell, I'd love to know Sonos's ethernet adoption rate, since they certainly have that data. I'd bet it's fairly high since Sonos is a bit up-market and sometimes professionally installed, or installed by enthusiasts, but I'm willing to guess it's < 5%, and realistically, < 1%, even if we only obviously limit the sample size to "Sonos devices that are eth capable."




Just last year I moved to a new home and was installing ethernet around the house. I could've easily made an extra port or two in the kitchen.

I generally like receiving a notification when the dishwasher is finished with the dishes, but with the current WiFi setup it's always broken and I don't have the energy to fix it. So I would've used it if it were working over Ethernet and I'm not using it now when it can only work over WiFi.

Out of home automation devices Philips Hue works only over Ethernet, though there you have the advantage that you can place the hub anywhere you like.


You can say that about anything though. Most people aren't writing code or building binaries, so you might as well take the ability of the end user to write code or run any unsigned unauthorized executables on their PCs. Also most people aren't running old ass executables, so screw backwards compatibility too. I'm sure it will make operating systems a lot less complex if you do down that path, but most people here would revolt if that was done by any OS vendor.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: