Sjmarf@sh.itjust.works to Programmer Humor@programming.dev · 2 years agoLDACsh.itjust.worksimagemessage-square76fedilinkarrow-up1714arrow-down14
arrow-up1710arrow-down1imageLDACsh.itjust.worksSjmarf@sh.itjust.works to Programmer Humor@programming.dev · 2 years agomessage-square76fedilink
minus-squareKairuByte@lemmy.dbzer0.comlinkfedilinkarrow-up36·2 years agoBluetooth as a whole is kind of a mess if we’re being honest.
minus-squarecmnybo@discuss.tchncs.delinkfedilinkEnglisharrow-up18·2 years agoThat’s what happens when you have a 25 year old protocol and try to maintain backwards compatibility through all of the versions.
minus-squareComment105@lemm.eelinkfedilinkarrow-up6·edit-22 years agoThe world of audio would be more of a mess if Bluetooth was developed scrapped and replaced according to what seems to be your recommendations. I’m glad they did it the way they did. It’s not time for change. Just alternatives for snobs.
minus-squaretabularasa@lemmy.calinkfedilinkarrow-up12·2 years agoCan we name a more poorly implemented protocol? Probably. One used as much as Bluetooth? Probably not.
minus-squareOnomatopoeia@lemmy.cafelinkfedilinkEnglisharrow-up6·2 years agoComes from being a compromise “standard”. The name says it all, being named after a king that brought multiple tribes together.
Bluetooth as a whole is kind of a mess if we’re being honest.
That’s what happens when you have a 25 year old protocol and try to maintain backwards compatibility through all of the versions.
The world of audio would be more of a mess if Bluetooth was developed scrapped and replaced according to what seems to be your recommendations. I’m glad they did it the way they did.
It’s not time for change. Just alternatives for snobs.
Can we name a more poorly implemented protocol? Probably. One used as much as Bluetooth? Probably not.
NAT
Comes from being a compromise “standard”. The name says it all, being named after a king that brought multiple tribes together.