![]() This kind of thing was the cause of the multiple "print nightmare" scenarios that Microsoft inevitably but indirectly created. It doesn't help that many of these hardware manufacturers seemed to employ the least well paid rooms of monkeys to mash keyboards until, with compiler warnings turned off, the driver code compiled and was therefore considered complete. Instead, device manufacturers had to cobble together their own custom hacks into the system in order to implement what is usually very similar functionality to other printers but named and implemented entirely differently. Microsoft could have created common extensions, with an easy and common extension implementation but they didn't. ![]() Microsoft have also been very, very slow to work with changes and functions in printers and, in particular, multi-function devices. The core applications in Microsoft 365 don't even do print preview consistently, what hope is there for others? Microsoft didn't do this and instead forced every application developer, including their own, to have to cobble together custom and inconsistent print preview functionality. For example, print preview could have been a standard function for any application - although potentially not all printing devices may have been able to support it. Microsoft had an opportunity to do a good thing with printing, but they chose not to. the deeply unfashionable side of Microsoft's development that has been rolling around in Microsoft's self-made development hell for many years.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |