The ISO 7-Layer model was the starting point for interpretation of the model. The diversity of platforms and technologies spanned both the network layer and the language set utilized by the operating system AND database. These inter-complexities were a hardy challenge to debug and further implement.
I’ll not list all platforms and operating systems or databases. These still live in the PAM today.
AppleTalk, NetWare, Microsoft, IBM, Novell all had different TCP stacks for network communication.
DB3, TXT, ORA, SYB, INF, MSS - all databases with their own functional peculiarities and implicit value to the growing information technology business-scape.
The ability to write in one place and run on soo many devices. Do I dare mention other runtimes still around today?
The Refresh’ing-er
Seeing UNIFACE today these concepts evolved very nicely. Containerizations, purpose-built runtimes, security-enforcement, platform-independent integration capabilities, Wow! In UTF8/16-Unicode;→
Inside automation has taken many paths since this engineer has been a teenager. (well, actually a 20-something) JavaScript was a new ‘toy’ when I was working deeply in UNIFACE. It has now graduated to TypeScript! (still compiles to JavaScript) Funny thing, a class-less no-model data scripting language adopted a model semantic for enforcing data security and quality, sounds oddly familiar! Databases have gone from relational to non-relational and back again to relational to realize the data value. AI is the weighted relational amalgamation of a set of non-relational queries tied together by relational context -- different knowledge-in to knowledge-out but now super-highly refined!
These paths are intertwining again!
I look forward to stirring some new conversation here working with Software Imaging Ltd. Please let me know where the “good places” to check out are!
Those in the space may recognize me from times past -- 5,6,7,8...10! Let’s connect! “Software craftsman and agile collaborator” - Robert Kranson
