5 ms·
I'd really like to have some specific example, because while apple never kept much backward compatibility, I've not eared of or being impacted much by supported
by tuyiown 3y ago
I'd really like to have some specific example, because while apple never kept much backward compatibility, I've not eared of or being impacted much by supported API changes when used in intended ways.
The actual thing you can praise MS for is to respect the «all observable behaviors» in their backward compatibility or support. Apple never ever gave in that way, only that you are supposed to use things as expected or expect to be punished. Not that they have stellar track records on that front either, there are tons of old code that still work out there.
- VyseofArcadia 3y agoThe specific example I remember (because I'm the one that fixed it) had something to do with how Image I/O handled TGA images. I don't remember all the details, but it was definitely not the case that we were misusing the API. Per the documentation everything had been above board, and everything was still above board. The images causing the issue were well-formed. Just something subtly changed with the CGImageSource API for TGA images specifically that required finding a workaround. Why that customer was using TGA images in their workflow in the 2010s I'll never know.
- tuyiown 3y agoHa. I can see how macOS can be an awful platform for those kinds of requirements. Thanks for your answer.