4 ms·
Bluetooth has sucked since it was introduced. I've never had a Bluetooth anything that worked well and reliably. We need a total rethink on close-range wireles
by SoftTalker 2y ago
Bluetooth has sucked since it was introduced. I've never had a Bluetooth anything that worked well and reliably.
We need a total rethink on close-range wireless communication for accessory devices. Preferably something patented with an expensive license so fly-by-night chinese hardware shops can't dump their garbage on the market using that protocol.
- 6SixTy 2y agoThere is an alternative protocol for wireless communications, only problem is that it's Chinese. https://news.ycombinator.com/item?id=42443750 https://news.ycombinator.com/item?id=42443750
- lesuorac 2y agoAren't like all of the Bluetooths alternative wireless protocols to themselves? It's not like you can use a Bluetooth classic device to connect to Bluetooth low energy. Then there's also like Zigbee and etc; I don't think the world is hurting for wireless protocols. Everybody has their own new standard that'll be able to replace the rest lol.
- 6SixTy 2y agoDifference is that Zigbee etc aren't vying for the same place that StarFlash/Nearlink,etc is for Bluetooth
- jwr 2y agoThat kind of generalizing isn't helpful and isn't true, either. I am sorry you didn't have a "Bluetooth anything" that worked reliably. I did. In fact, everything that I own that uses Bluetooth works very well. There are two important things about Bluetooth. 1. There are actually two kinds of Bluetooth. The "traditional" mostly connection-oriented Bluetooth and BLE (Bluetooth Low Energy). They share very little with each other, except for the marketing name. BLE works way better in practice. Many people still remember their old headsets that used Bluetooth and that took ages to connect to their phones and associate those with the "Bluetooth experience". 2. Bluetooth is complex. Many manufacturers get it wrong. But the problem is not with Bluetooth. You could invent a different set of protocols, and if they were to do everything that Bluetooth does, they would get very complex as well, and we would have the same problem, except in a less popular and less broadly adopted protocol.
- ryandrake 2y ago> Many manufacturers get it wrong. But the problem is not with Bluetooth. To the end user, this is kind of a distinction without a difference. The end user doesn't care whether it's Bluetooth, The Standard that's bad or Bluetooth, the Implementation. He just knows that when he has to use Bluetooth, he's probably going to have problems. I've worked with BLE implementation developers and I've heard the stack described as a "Layer cake of sorrow." There are major problems with it, and by "It" I mean the entire bag containing the specification, all the various implementations, and the hardware ecosystem. All of these things combined define Bluetooth in people's minds.
- darkerside 2y agoHN is traditionally the kind of place where unpacking that nuance is rewarded, not dismissed
- ryandrake 2y agoYes, it's useful for technical folks to understand the real difference, but I'm saying the end user doesn't care.
- hedora 2y agoBut if the spec as a whole is bad, all layers of the spec are bad, the implementations are all bad, and the user experience is bad, then in what way can Bluetooth be described as anything but bad?
- jwr 2y ago> if the spec as a whole is bad, all layers of the spec are bad, This discussion is intriguing. I wonder how many people commenting on "the spec" have actually read any part of "the spec" in question (I have). And since we're posting anecdata: I can't think of a single problem I've had with a Bluetooth device in recent years, and I use a lot of Bluetooth devices. So this kind of generalizing doesn't help. As a counterpoint, every embedded device that uses Wi-Fi promises a world of pain. The bizarre pairing procedures, connecting to temporary access points, entering passwords — it's all a combination of pain, timeouts, problems, and resets. But that doesn't lead me to state that "wifi is bad, the spec as a whole is bad, all layers of the spec are bad, the implementations are all bad".