> Another implementation, that I feel is far fairer is allowing me to interface with Microsoft Word so I could develop an alternate route to repair whatever fun

> Another implementation, that I feel is far fairer is allowing me to interface with Microsoft Word so I could develop an alternate route to repair whatever functionality isn't working. I routinely encounter bugs in software that wouldn't be fixable with some API. How about something like "it crashes on startup when I have graphics driver X installed" for example, if it turns out to be due to a bug in Word rather than in the graphics driver? This is the sort of weird interaction that usually leads to me wanting to fix things. IME, API access tends to be about additional functionality or integrations, not bugfixing. I equate "right to repair" with the latter, not the former.