Sjmarf@sh.itjust.works to Programmer Humor@programming.dev · 3 days agoLDACsh.itjust.worksimagemessage-square108fedilinkarrow-up1787
arrow-up1787imageLDACsh.itjust.worksSjmarf@sh.itjust.works to Programmer Humor@programming.dev · 3 days agomessage-square108fedilink
minus-squareKairuByte@lemmy.dbzer0.comlinkfedilinkarrow-up39·3 days agoBluetooth as a whole is kind of a mess if we’re being honest.
minus-squarecmnybo@discuss.tchncs.delinkfedilinkEnglisharrow-up21·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-squaretabularasa@lemmy.calinkfedilinkarrow-up11·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.
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.