Tool kits which don’t use native OS widgets and which do not honour settings which the user has gone to the effort to make, annoy me.
Such fragmentation is an active dis-service to the user, and the reason why we don’t have nice things such as resolution-independent interfaces which just work.
Next time you’re at a Windows box, customize the interface, including screen DPI, then launch WordPad and see how it respects said settings, then ask yourself how you feel about programmers who don’t adhere to the guidelines which result in such consistency.
While a foolish inconsistency may be the hobgoblin of a little mind, an inconsistency which fails to adhere to published guidelines, and which creates even greater inconsistency represents a conscious choice to fragment a given operating system’s interface, and which interfere w/ the ideal of computers serving as “Bicycles for the Mind”.
It kills me that the high water mark of my computing experience was back when I used an NCR-3125 running PenPoint, cabling up to a NeXT Cube over a serial connection to transfer .rtf and .eps files. Being able to use TeXview.app’s TeX EQ to EPS Service in Virtuoso.app or FrameMaker “just worked” as did everything else on the system. Oh well, at least my NCR is being preserved by the Smithsonian.
This current mish-mash of tool kits and programming systems feels like a hair shirt by comparison every time I bump up onto some inconsistency, and it makes me wish that I’d bought a Bridge City Tools JointMaker Pro instead of a ShapeOko.
Edit: Oh well, once the Linux version is released, I can just run everything in a Linux environment, using only QT toolkit apps there, which hopefully won’t offend my delicate sensibilities.