Sjmarf@sh.itjust.works to Programmer Humor@programming.dev · 4 months agoLDACsh.itjust.worksimagemessage-square117linkfedilinkarrow-up1841arrow-down14
arrow-up1837arrow-down1imageLDACsh.itjust.worksSjmarf@sh.itjust.works to Programmer Humor@programming.dev · 4 months agomessage-square117linkfedilink
minus-squareKairuByte@lemmy.dbzer0.comlinkfedilinkarrow-up38·4 months agoBluetooth as a whole is kind of a mess if we’re being honest.
minus-squarecmnybo@discuss.tchncs.delinkfedilinkEnglisharrow-up22·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-squareComment105@lemm.eelinkfedilinkarrow-up6·4 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.
minus-squaretabularasa@lemmy.calinkfedilinkarrow-up12·4 months agoCan we name a more poorly implemented protocol? Probably. One used as much as Bluetooth? Probably not.
minus-squareOnomatopoeia@lemmy.cafelinkfedilinkEnglisharrow-up6·4 months 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.
Can we name a more poorly implemented protocol? Probably. One used as much as Bluetooth? Probably not.
SMTP?
NAT
Comes from being a compromise “standard”. The name says it all, being named after a king that brought multiple tribes together.