Sjmarf to Programmer Humor@programming.dev • 4 months agoLDACsh.itjust.worksimagemessage-square111fedilinkarrow-up10arrow-down10
arrow-up10arrow-down1imageLDACsh.itjust.worksSjmarf to Programmer Humor@programming.dev • 4 months agomessage-square111fedilink
minus-square@KairuByte@lemmy.dbzer0.comlinkfedilink0•4 months agoBluetooth as a whole is kind of a mess if we’re being honest.
minus-square@Onomatopoeia@lemmy.cafelinkfedilinkEnglish0•4 months agoComes from being a compromise “standard”. The name says it all, being named after a king that brought multiple tribes together.
minus-square@tabularasa@lemmy.calinkfedilink0•4 months agoCan we name a more poorly implemented protocol? Probably. One used as much as Bluetooth? Probably not.
minus-square@cmnybo@discuss.tchncs.delinkfedilinkEnglish0•4 months agoThat’s what happens when you have a 25 year old protocol and try to maintain backwards compatibility through all of the versions.
minus-square@Comment105@lemm.eelinkfedilink0•edit-24 months 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.
Bluetooth as a whole is kind of a mess if we’re being honest.
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
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.