Editing Oberon (operating system) (section)

===Plugin Oberon and ''slim binaries''===
A version of the Oberon System 3,<ref name="Sys3"/> which is more integrated in the Microsoft Windows OS than other implementations was named Plugin Oberon.<ref>{{Cite web |url=http://e-collection.library.ethz.ch/eserv/eth:26257/eth-26257-02.pdf |title=Fine-grained integration of Oberon into Windows using pluggable objects |last=Zeller |first=Emil Johann |date=2002}}</ref> Plugin Oberon had support for [[Object Linking and Embedding|OLE]], [[NPAPI|Netscape Plugins]], and the binary format named Oberon Module Interchange (OMI) or ''slim binaries'', which allowed portable object code between Intel [[x86]], Motorola [[68K]], and [[PowerPC]] architectures. Slim binaries were invented by [[Michael Franz]] in the early 1990s. They were motivated and opposed to the ''fat binaries'' invented by Apple during the transition from 68k to PowerPC architectures.<ref name="OMI">{{Cite book |last=Franz |first=Michael |date=1 March 1994 |title=Code-Generation On-the-Fly: A Key to Portable Software |publisher=Verlag der Fachvereine Hochschulverlag AG an der ETH Zurich |location=Zürich |isbn=978-3728121158}}</ref> OMI provided portable code based on a compressed version of the abstract syntax tree. The approach of a compressed abstract syntax tree for portable code representation is revived in the [[Java (programming language)|Java]] world for [[GraalVM]] and [[GraalVM#Truffle Language Implementation Framework|Truffle]].