Earlier quoted context omitted.
I think Apple was the one who was unreasonable here, not Adobe. I loathe the idea of giving Microsoft credit for anything, but one thing they got right was their focus on backward compatibility. Certainly that has frayed at times here and there, but MS generally doesn't ask their developers to completely rewrite their applications to use a new application framework.
And because of that, even as far back as 2005, there were 10 ways to create a string in C and depending on which Windows API you were using, you had to convert between them constantly. Considering how Microsoft has failed to move past Windows while Apple uses the same OS more or less for watches, phones, tablets, monitors, set top boxes, etc without having to support legacy crap.
That's pretty easy when you have no qualms whatsoever about breaking support for software which is older than 2-3 years and offer very limited support for third party software on all of your platforms except one.