3 ms·
I got my start programming with a tool that originated on mainframes, saw a brief popularity in text-based minicomputers (Vaxen and Unixen), was ported to X11 U
by dredmorbius 5y ago
I got my start programming with a tool that originated on mainframes, saw a brief popularity in text-based minicomputers (Vaxen and Unixen), was ported to X11 Unix, then to PCs beginning with MS Windows 3, and through multiple generations as that became the overwhelmingly dominant user platform.
There were further changes and inheretences from within each of those environments as well.
It was possible when using the application to recognise where and how various components and features originated and what platform(s) they were developed on or for. Even some 50 years after the first release, this can be determined.
As I came to use Unix and Linux more heavily, I noticed the same trend in various applications, both command-line (GNU and BSD userland, MVS JCL relics such as "dd", and others) and graphical. Various X11 and graphical toolkits became instantly recognisable, and though the appearances (and often feature locations and implementations) were often wildly inconsistent (Xt Intrinsics / Athena scrollbars, anyone?), once the contexts were known, the visual indicators made clear "oh, this is an Athena app, this is a Motif app, this is a gtk app, this is a KDE app", or singletons (Netscape / Mozilla / Phoenix / Fireox, StarOffice / OpenOffice / NeoOffice / LibreOffice, Applixware (remember that?), etc. came to be known quantities. Various JS toolkits and Electron apps are probably the current version of this.
I've (mostly in jest, though possibly more seriously with time) had the tag "technological archaeologist" in various online bios. That traces directly to my experience with tools developed over a number of different platforms or tools. Or simply the influences of time and trends or fashions.
Microsoft Windows at about 45 years of age now has its own design legacy and archaeological strata.