Annotation of papers/freem_history/freem_history.ms, revision 1.12

1.2       snw         1: \"
1.12    ! snw         2: \" $Id: freem_history.ms,v 1.11 2025/04/23 18:58:31 snw Exp $
1.2       snw         3: \"  History of FreeM
                      4: \"
                      5: \" Copyright (C) 2025 Serena Willis
                      6: \"
1.3       snw         7: \"   $Log: freem_history.ms,v $
1.12    ! snw         8: \"   Revision 1.11  2025/04/23 18:58:31  snw
        !             9: \"   Refine awkward paragraphing
        !            10: \"
1.11      snw        11: \"   Revision 1.10  2025/04/23 18:44:26  snw
                     12: \"   Correct capitalization error in abstract
                     13: \"
1.10      snw        14: \"   Revision 1.9  2025/04/23 18:40:00  snw
                     15: \"   Improve footnotes
                     16: \"
1.9       snw        17: \"   Revision 1.8  2025/04/23 15:12:13  snw
                     18: \"   Improve wording
                     19: \"
1.8       snw        20: \"   Revision 1.7  2025/04/23 15:05:45  snw
                     21: \"   Fix typographical problems
                     22: \"
1.7       snw        23: \"   Revision 1.6  2025/04/23 13:32:34  snw
                     24: \"   Fix copyright symbol
                     25: \"
1.6       snw        26: \"   Revision 1.5  2025/04/23 13:29:37  snw
                     27: \"   Add copyright and license, shorten URLs
                     28: \"
1.5       snw        29: \"   Revision 1.4  2025/04/22 18:16:06  snw
                     30: \"   Remove references to FreeM as a database
                     31: \"
1.4       snw        32: \"   Revision 1.3  2025/04/22 17:54:09  snw
                     33: \"   Initial draft of FreeM History paper
                     34: \"
1.3       snw        35: \"   Revision 1.2  2025/04/22 14:56:22  snw
                     36: \"   Add comment header to FreeM History
1.2       snw        37: \"
1.3       snw        38: \"
                     39: .R1
                     40: database ../references.bib
                     41: move-punctuation
                     42: .R2
1.1       snw        43: .TL
                     44: The History of FreeM
                     45: .AU
                     46: Serena Willis
                     47: .AI
                     48: Coherent Logic Development
                     49: .AB
1.10      snw        50: Since 2014, the author has been the maintainer of the primary fork of the FreeM implementation of the M programming language and persistent global storage engine. In this paper, we will share some of the history of FreeM, as well as its current status and goals.
1.1       snw        51: .AE
                     52: .SH
                     53: Initial Involvement
                     54: .PP
1.12    ! snw        55: The author's mentor in computer programming and UNIX was Lawrence Landis, who involved himself heavily in the M programming language ca. 1991. Mr. Landis promoted the M language to the author from 1991 forward, and first demonstrated FreeM to her in August 1998. In 2010, the author incorporated her company, Coherent Logic Development, learned M, and began doing contract work in M through Mr. Landis's company, Fourth Watch Software.
1.1       snw        56: .PP
1.3       snw        57: Mr. Landis was the owner of FreeM's SourceForge repository
                     58: .[
                     59: gumpSF
                     60: .]
                     61: , which had not been touched in a number of years, following Fidelity National Information Services' decision to release GT.M under a free software license. In August 2011, the author downloaded the source code for FreeM and did enough work on it to enable building and running under modern GNU/Linux systems and posted it to the mumpster.org forums.
                     62: .[
                     63: freem014
                     64: .]
1.1       snw        65: .PP
                     66: In 2014, Mr. Landis gave the author administrator access to the FreeM SourceForge repository and transferred maintainership of the project to her.
1.3       snw        67: .[
                     68: gumpSF
                     69: .]
1.1       snw        70: .SH
                     71: Early History
                     72: .PP
1.3       snw        73: FreeM was developed in Germany in the mid-1990s by a developer who went by the pseudonym \fIShalom ha-Ashkenaz\fR, whose actual identity remains unknown,
                     74: .[
1.9       snw        75: walters99
                     76: %P 19
1.3       snw        77: .]
1.11      snw        78: though it is thought by some that they are a dentist who learned C and developed FreeM on their own time. Shalom developed FreeM at a time when InterSystems Corporation (the company that developed the ISM implementation of M) was acquiring the majority of its competitors and shutting them down.
1.3       snw        79: .[
1.9       snw        80: ibid
                     81: %P 18
1.3       snw        82: .]
                     83: . Shalom wished to provide a community-driven, open-source implementation of M as a bulwark against the growing threat of single-vendor hegemony over the M language. Its design\(emas well as some of the documentation included with the original sources\(emindicate that FreeM was originally targeted to the MS-DOS family of operating systems. It made use of a very limited subset of the C library, and included instructions for renaming the MS-DOS style 8.3 filenames in order to compile under UNIX.
                     84: .[
                     85: freemREADME
                     86: .]
1.5       snw        87: .KS
1.3       snw        88: .PP
                     89: At one point in FreeM's early history, Shalom ported FreeM from MS-DOS to SCO UNIX, the UNIX System V Release III-derived descendant of Microsoft XENIX, now known as SCO OpenServer\(ema platform still supported by FreeM today.
                     90: .[
                     91: portSCO
                     92: .]
                     93: This port brought support for the \fIscoansi\fR terminal type, including colors and ANSI X3.64 control mnemonics.
1.5       snw        94: .KE
1.1       snw        95: .SH
1.11      snw        96: Generic Universal M Project
1.1       snw        97: .PP
1.5       snw        98: The \fIGeneric Universal M Project\fR was conceived by Richard F. Walters, a professor from U.C. Davis. The GUMP, following the rising popularity of object-oriented programming in the 1990s, was intended to be a toolkit allowing M implementations to be built from discrete components with a well-defined and well-specified public interface among these components. These components included the global handler (supplying the functionality of persistent global storage), and the interpreter/compiler (responsible for implementing M language commands). The components would have been able to communicate over a network, or in-process on the same host, enabling distributed computing functionality.
1.3       snw        99: .[
                    100: c2m
                    101: .]
                    102: .PP
                    103: Although the specification for the GUM interface to global handlers attained a reasonably well-specified level of completeness,
                    104: .[
                    105: gumapi
                    106: .]
1.9       snw       107: and Lawrence Landis and others developed a mostly-complete implementation of a GUM global handler,
1.3       snw       108: .[
                    109: gumpsrc
                    110: .]
                    111: none of the other envisioned components were ever completed, and specifically, the interpreter component was missing.
1.1       snw       112: .SH
                    113: Shalom's Gift
                    114: .PP
1.5       snw       115: In July of 1998, Shalom ha-Ashkenaz donated the FreeM source code (then known as FreeMUMPS) to the M User's Group-Deutschland (MUG-D), hoping the community would take the nascent implementation from its infancy through to a state of production-ready completeness and robustness. Shalom also placed a few conditions on his gift: a public release could not be made until a substantial set of milestones were reached. Per his conditions, the FreeMUMPS project must:
1.3       snw       116: .[
                    117: freemREADME
                    118: .]
1.1       snw       119: .IP \(bu 2
                    120: Implement the entirety of \fIANSI X11.1-1995\fR
                    121: .IP \(bu 2
                    122: Use Structured System Variables instead of \fIVIEW\fR commands and \fI$VIEW\fR functions
                    123: .IP \(bu 2
                    124: Raise the string size limits
                    125: .IP \(bu 2
                    126: Implement MWAPI, OMI, X11 bindings, and GKS bindings
                    127: .IP \(bu 2
                    128: Be substantially free of major bugs
                    129: .PP
                    130: Although MUG-D readily accepted the contribution of FreeMUMPS, the organization itself lacked the manpower and expertise to complete the implementation. Just as it is now, the intersection of M community members who know enough of the M language and C language to work on a project this ambitious was quite small.
1.11      snw       131: .SH
1.7       snw       132: .KS
1.1       snw       133: Merging GUMP and FreeM
                    134: .PP
1.5       snw       135: Very shortly after the contribution of FreeMUMPS to MUG-D, Richard F. Walters and a small team of developers and administrative staff who had been working on the GUMP assumed maintainership of the FreeMUMPS source code, with Lawrence Landis managing the development efforts.
1.3       snw       136: .[
1.9       snw       137: shortWalters99
                    138: %P 19
1.3       snw       139: .]
                    140: This included representatives from the \fIM Technology Association\fR (an M vendor association having several foreign branches), the \fIM Development Committee\fR (the M standards organization hosting the ANSI/ISO standards for the M language, then sponsored by the M Technology Association), and others.
                    141: .[
                    142: freemContributors
                    143: .]
                    144: The goals of this team were to:
1.1       snw       145: .IP \(bu 2
                    146: Meet Shalom's requirements for a public release of FreeMUMPS
                    147: .IP \(bu 2
                    148: Convert FreeMUMPS into the first interpreter component of the GUMP
1.11      snw       149: .KE
1.1       snw       150: .PP
1.5       snw       151: During this period, Ronald L. Fox of Diagnostic Laboratory Services in Honolulu, HI (who passed in 2010)
1.3       snw       152: .[
                    153: ronFoxGrave
                    154: .]
                    155: ported FreeMUMPS from SCO UNIX to Red Hat 5 and glibc-6.
                    156: .[
                    157: ronFoxPort
                    158: .]
                    159: Steve "Saintly" Zeck of the U.C. Davis Veterinary Medical Teaching Hospital
                    160: .[
                    161: saintlyBio
                    162: .]
                    163: also attempted to rewrite the symbol table code to lift string size limits,
                    164: .[
                    165: saintlySymtab
                    166: .]
1.8       snw       167: David Whitten enhanced some of the implementation-specific extensions, and Lawrence Landis integrated Zeck's symbol table work.
1.3       snw       168: .PP
1.5       snw       169: In FreeM 0.1.0, the name of the implementation was changed from FreeMUMPS to Public Standard M, and again to Free Standard MUMPS and then FreeM when it was discovered leading up to the FreeM 0.2.0 release that the PSM acronym was already in use for Patterson & Gray's
1.3       snw       170: .[
                    171: mdc_implementations
                    172: .]
                    173: M implementation.
                    174: .[
                    175: Changes.GUM
                    176: .]
                    177: Dr. Walters also received the implementation ID of 49 from then secretary of the M Development Committee, Don Piccone.
                    178: .[
1.9       snw       179: ibid
1.3       snw       180: .]
1.1       snw       181: .PP
1.5       snw       182: One of the contributors to FreeM at this stage\(emprimarily in the area of M vendor routines\(emwas Axel Trocha, who would later maintain a private fork of FreeM.
1.3       snw       183: .[
                    184: trochaFork
                    185: .]
1.7       snw       186: .KS
1.1       snw       187: .SH
                    188: The GT.M Free Software Release
                    189: .PP
                    190: GT.M, an acronym for \fIGreystone Technology MUMPS\fR, is an M implementation that was released by Greystone Technology in 1986. Greystone was later acquired by Sanchez Computer Associates, which was in turn acquired by Fidelity National Information Services.
1.3       snw       191: .[
                    192: fisSanchezAcquisition
                    193: .]
                    194: .PP
                    195: When GT.M was released under the GNU General Public License in 2000,
                    196: .[
                    197: gtmRelease
                    198: .]
1.5       snw       199: it seemed to many to negate the entire \fIraison d'etre\fR for FreeM, as GT.M was a well-established, robust, and high-performance M implementation with which FreeM could not then compete. Unfortunately, at this time, the GUMP and FreeM projects lost all of their momentum, and new development along these lines rapidly ceased. The final GUMP team release of FreeM was 0.5.0.
1.3       snw       200: .[
                    201: freem050
                    202: .]
                    203: However, Axel Trocha's private port would continue to be developed for some years.
1.7       snw       204: .KE
1.1       snw       205: .SH
                    206: Axel Trocha's Fork
                    207: .PP
1.11      snw       208: When the free software release of GT.M stalled the GUMP team's progress on the primary branch of development, Axel Trocha, an aforementioned contributor, continued development on the FreeM source code. Trocha added many interesting features to the FreeM codebase, including:
1.1       snw       209: .IP \(bu 2
                    210: A native port to Microsoft Windows
                    211: .IP \(bu 2
                    212: Compiling FreeM as an Apache web server module, allowing FreeM to be used easily for web development
                    213: .IP \(bu 2
                    214: The ability to output HTML code in a heredoc-style format, with any line of code beginning with a left angle bracket being interpreted as HTML with support for interpolated M locals and globals
                    215: .IP \(bu 2
                    216: Extensions allowing FreeM to be used as a command-line shell, along the lines of UNIX \fIbash\fR, Windows \fIcmd.exe\fR, etc.
                    217: .PP
1.5       snw       218: Trocha also maintains ownership of the \fIfreem.net\fR Internet domain,
1.3       snw       219: .[
                    220: trochaDomain
                    221: .]
1.5       snw       222: and continued issuing public releases of his FreeM port on that site until sometime after 2004, at which point this fork was made entirely private. Currently, freem.net is a blank page. However, trocha's fork of FreeM continues to the present as the back-end storage engine and programming environment for the www.elvenrunes.de website.
1.3       snw       223: .[
                    224: elvenRunes
                    225: .]
1.5       snw       226: The author has communicated with Mr. Trocha on occasion, and though he is supportive of the author's efforts, has chosen to remain in the background.
1.1       snw       227: .SH
                    228: Resuming Primary Development Branch
                    229: .PP
                    230: In 2011, the author downloaded the FreeM source code from the GUM Project's SourceForge repository\(emdormant since 2000\(emand updated it just enough that it would compile and run on modern GNU/Linux systems. The author also quickly updated FreeM to support terminal sizes larger than 80x24.
                    231: .SH
                    232: Taking Maintainership
                    233: .PP
1.5       snw       234: In 2014, Lawrence Landis transferred administrative access of the GUMP repository, conferring maintainership of the primary branch of FreeM development to the author. Since then, many features have been added and many bugs corrected, including:
1.3       snw       235: .IP \(bu 2
                    236: Adding support for proper namespaces, configured through a \fIfreem.conf\fR file, which standardizes routine and global storage locations
                    237: .IP \(bu 2
                    238: Adding support for Structured System Variables
                    239: .IP \(bu 2
                    240: Adding support for the asynchronous event specification from MDC Type A proposal \fIX11/1998-28\fR
                    241: .[
                    242: x119828
                    243: .]
                    244: .IP \(bu 2
                    245: Adding support for constants via the \fICONST\fR keyword
                    246: .IP \(bu 2
                    247: Adding a \fIWITH\fR command allowing the specification of an implicit prefix to all subsequent variable references
                    248: .IP \(bu 2
                    249: Adding a runtime \fIWATCH\fR command, tracking changes to specified local or global variables
                    250: .IP \(bu 2
                    251: Adding an \fIASSERT\fR command, which will fail with an error message if the following expression evaluates \fIfalse\fR
                    252: .IP \(bu 2
                    253: Removing the Steve Zeck symbol table implementation\(emwhich was unreliable\(emand reverting to the original implementation
                    254: .IP \(bu 2
                    255: Adding support for the GNU \fIreadline\fR library, with persistent command line history and editing
                    256: .IP \(bu 2
                    257: Adding REPL-like functionality (in direct mode, any M expression beginning with a number will be prepended with an implicit \fIWRITE\fR)
                    258: .IP \(bu 2
                    259: Adding transaction processing
                    260: .IP \(bu 2
                    261: Adding \fIKVALUE\fR and \fIKSUBSCRIPTS\fR
                    262: .IP \(bu 2
                    263: Preparing to support the \fIM Windowing API\fR (MWAPI)
                    264: .IP \(bu 2
                    265: Adding the \fIfmadm\fR command-line utility, for system administration functions
                    266: .IP \(bu 2
                    267: Adding support for after-image journaling and forward recovery of globals
1.5       snw       268: .KS
1.3       snw       269: .IP \(bu 2
                    270: Writing a \fItexinfo\fR manual, from which the HTML manual is derived
                    271: .IP \(bu 2
                    272: Porting to Solaris/SPARC, Solaris/x86, Linux/s390x, Linux/armv6l, Linux/armv7l, SCO OpenServer 5.0.7, Tru64 UNIX/alpha, AIX/ppc, Mac OS X/x86, GNU HURD, Cygwin, NetBSD, FreeBSD, OpenBSD, and WSL1/2
1.11      snw       273: 
1.5       snw       274: In addition, the FreeM web site
1.3       snw       275: .[
                    276: freemWebsite
                    277: .]
                    278: was created, to distribute downloads and documentation.
1.5       snw       279: .KE
1.3       snw       280: .SH
                    281: Future
                    282: .PP
1.5       snw       283: FreeM is envisioned as a client-oriented desktop M implementation, for developing graphical user interfaces that will run on mobile and desktop devices.
1.3       snw       284: .PP
                    285: The author also intends to adopt the original vision of the GUMP team, dividing FreeM's functionality into discrete components having a well-specified public interface, with the ability to run in distributed computing environments over a network.
                    286: .PP
                    287: FreeM's mission is to advance the state-of-the-art in M implementations, and push the evolution of the language forward. Maintaining portability to as many vintage and modern UNIX systems as possible is held as a high priority, while portability of M routines and MDC standards compliance will be maintained through the use of the new \fI$ZDIALECT\fR intrinsic special variable to ensure that such compliance does not conflict with the primary goal of elegantly advancing the state-of-the-art and finding new audiences for the concepts originated by Neil Pappalardo and Octo Barnett in 1966.
                    288: .PP
                    289: The FreeM project is also strongly committed to free software principles, and is firmly aligned with the goals of the GNU Project and the Free Software Foundation, believing that the ethical concerns surrounding proprietary software are at least as important as the practical concerns espoused by the Open Source movement.
                    290: .[
                    291: whyFreeSoftware
                    292: .]
1.5       snw       293: .SH
                    294: Conclusion
                    295: .PP
1.7       snw       296: FreeM has seen a colorful and turbulent history, touched by many capable hands. Though public development of any strain of the implementation was dormant for nearly a decade, fourteen years of almost continuous development have passed since the project resumed in 2011, and a decade since official maintainership passed in 2014, and great progress has been made.
                    297: .PP
                    298: FreeM\(emas is the case for all M projects\(empresses forward in a period where the future of the M programming language is uncertain. M Development Committee efforts concurrent with FreeM development have been sporadic and have missed many milestones, the community's most prominent members are aging, and many organizations have migrated from large M applications to what is perceived as more "modern" replacements.
                    299: .PP
                    300: It is the opinion of the author that the tight integration of an expressive and dynamic language with a robust and performant persistent storage engine makes M a natural candidate for many new and general applications. Modern application development is plagued by overwhelming bars to entry, requiring mastery of many languages and database management systems and the bulky interfaces connecting them.
                    301: .PP
1.11      snw       302: Though not without significant warts accreted over the years, M has no such overhead. Thus, FreeM seeks to press its philosophical advantages by mitigating the language's accumulated cruft, and adding clean interfaces addressing the needs of today. With these goals in mind, development proceeds apace.
1.7       snw       303: .KS
1.5       snw       304: .SH
                    305: Copyright and License
                    306: .LP
1.6       snw       307: This document is Copyright \[co] 2025 Serena Willis
1.5       snw       308: .LP
                    309: Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License,
                    310: .[
                    311: gfdl
                    312: .]
                    313: Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover texts, and with no Back-Cover Texts. 
                    314: .LP
1.12    ! snw       315: \fI$Id: freem_history.ms,v 1.11 2025/04/23 18:58:31 snw Exp $\fR
1.7       snw       316: .KE

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>