Sjmarf@sh.itjust.works to Programmer Humor@programming.dev · 3 days agoLDACsh.itjust.worksimagemessage-square114fedilinkarrow-up1817arrow-down13
arrow-up1814arrow-down1imageLDACsh.itjust.worksSjmarf@sh.itjust.works to Programmer Humor@programming.dev · 3 days agomessage-square114fedilink
minus-squareKairuByte@lemmy.dbzer0.comlinkfedilinkarrow-up39·3 days agoBluetooth as a whole is kind of a mess if we’re being honest.
minus-squarecmnybolinkfedilinkEnglisharrow-up22·3 days 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 days 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·3 days agoCan we name a more poorly implemented protocol? Probably. One used as much as Bluetooth? Probably not.
minus-squareOnomatopoeia@lemmy.cafelinkfedilinkEnglisharrow-up7·3 days 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
SMTP?
Comes from being a compromise “standard”. The name says it all, being named after a king that brought multiple tribes together.