←back to thread

219 points zdw | 1 comments | | HN request time: 0.2s | source
1. shelled ◴[] No.45897922[source]
I worked in BT almost a decade ago for 4-5 years. My first job. I had never worked close to the hardware. It was nice. Even though the work was not assembly-level close to hardware. Then the rot hit. I saw BT had been there more or less for decades and in one way or another it was going to remain there. The big bad world of backward compatibility and having to support older devices out in the wild was so crucial (as per the companies' POV and I am not judging it either way) that I realised I do not want to keep copying and pasting one line for a driver fix from one code base to 373 for different devices. Given it could have been improved with CI/CD and better source control (maybe!) but it was just not worth it.

Then the rest of the software world hit hard, and I saw, yet again, that the grass is green and that at least the world of BT had epic job safety, slow but stable growth, and best of all - no rush to fix something in the next 37 mins or millions of ad revenue will be lost.

But I see, as I had guessed, not much has changed "more or less" :)

I blame Apple as well, or both Apple and SIG for not making adoptions faster. But then Apple had nothing to worry about when it came to backward compatibility. So "Apple-rest" never really happened in a meaningful way, and whatever happened happened quite late.

(By the way there are more details on SIG portal if one is interested. Here are some https://www.bluetooth.com/bluetooth-core-6-2-feature-overvie... and https://www.bluetooth.com/blog/just-released-bluetooth-core-... and maybe follow from there)