Sjmarf@sh.itjust.works to Programmer Humor@programming.dev · 1 month agoLDACsh.itjust.worksimagemessage-square108fedilinkarrow-up10arrow-down10
arrow-up10arrow-down1imageLDACsh.itjust.worksSjmarf@sh.itjust.works to Programmer Humor@programming.dev · 1 month agomessage-square108fedilink
minus-squareKairuByte@lemmy.dbzer0.comlinkfedilinkarrow-up0·1 month agoBluetooth as a whole is kind of a mess if we’re being honest.
minus-squarecmnybo@discuss.tchncs.delinkfedilinkEnglisharrow-up0·30 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-up0·edit-230 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-squareOnomatopoeia@lemmy.cafelinkfedilinkEnglisharrow-up0·1 month agoComes from being a compromise “standard”. The name says it all, being named after a king that brought multiple tribes together.
minus-squaretabularasa@lemmy.calinkfedilinkarrow-up0·1 month agoCan we name a more poorly implemented protocol? Probably. One used as much as Bluetooth? Probably not.
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.
Comes from being a compromise “standard”. The name says it all, being named after a king that brought multiple tribes together.
Can we name a more poorly implemented protocol? Probably. One used as much as Bluetooth? Probably not.
SMTP?
NAT