5 ms·
No, it's not. Like what is described in the original post, it is they spirit. For example for the case with the printer and the xbox, they could have an explici
by greatgib 3y ago
No, it's not. Like what is described in the original post, it is they spirit.
For example for the case with the printer and the xbox, they could have an explicit obvious error for the application.
Then it is the task of the application dev to validate its application for target it will run on. If it is does not work, it does not work.
Otherwise, you will still have dozens of bugs and unexpected behaviors, so a crappy application.
And new app developers will have to build upon that. Imagine the next app developer, you have to take into account that a platform pretends to support printers when it is not the case. So you will do things like: if there is a printer api but i don't see a printer available (/connected), pretend that we can't print and don't show the button... and so on...
If you have doubts about that, you can read the history of the openxml format:
https://ooxmlisdefectivebydesign.blogspot.com/2007/08/microsoft-office-xml-formats-defective.html https://ooxmlisdefectivebydesign.blogspot.com/2007/08/micros...
- buttercraft 3y ago> they could have an explicit obvious error for the application. No, they can't. "The application" has already been written by a 3rd party who could be out of business for all we know. > If it is does not work, it does not work. Or you could let it keep working. Somebody might depend on it, and none of this is their fault.