Annotation of papers/freem_history/freem_history.ms, revision 1.14
1.2 snw 1: \"
1.14 ! snw 2: \" $Id: freem_history.ms,v 1.13 2025/04/24 01:31:13 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.14 ! snw 8: \" Revision 1.13 2025/04/24 01:31:13 snw
! 9: \" Add biblio checker
! 10: \"
1.13 snw 11: \" Revision 1.12 2025/04/23 18:59:53 snw
12: \" Refine wording
13: \"
1.12 snw 14: \" Revision 1.11 2025/04/23 18:58:31 snw
15: \" Refine awkward paragraphing
16: \"
1.11 snw 17: \" Revision 1.10 2025/04/23 18:44:26 snw
18: \" Correct capitalization error in abstract
19: \"
1.10 snw 20: \" Revision 1.9 2025/04/23 18:40:00 snw
21: \" Improve footnotes
22: \"
1.9 snw 23: \" Revision 1.8 2025/04/23 15:12:13 snw
24: \" Improve wording
25: \"
1.8 snw 26: \" Revision 1.7 2025/04/23 15:05:45 snw
27: \" Fix typographical problems
28: \"
1.7 snw 29: \" Revision 1.6 2025/04/23 13:32:34 snw
30: \" Fix copyright symbol
31: \"
1.6 snw 32: \" Revision 1.5 2025/04/23 13:29:37 snw
33: \" Add copyright and license, shorten URLs
34: \"
1.5 snw 35: \" Revision 1.4 2025/04/22 18:16:06 snw
36: \" Remove references to FreeM as a database
37: \"
1.4 snw 38: \" Revision 1.3 2025/04/22 17:54:09 snw
39: \" Initial draft of FreeM History paper
40: \"
1.3 snw 41: \" Revision 1.2 2025/04/22 14:56:22 snw
42: \" Add comment header to FreeM History
1.2 snw 43: \"
1.3 snw 44: \"
45: .R1
46: database ../references.bib
47: move-punctuation
48: .R2
1.1 snw 49: .TL
50: The History of FreeM
51: .AU
52: Serena Willis
53: .AI
54: Coherent Logic Development
55: .AB
1.10 snw 56: 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 57: .AE
58: .SH
59: Initial Involvement
60: .PP
1.12 snw 61: 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 62: .PP
1.3 snw 63: Mr. Landis was the owner of FreeM's SourceForge repository
64: .[
65: gumpSF
66: .]
67: , 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.
68: .[
69: freem014
70: .]
1.1 snw 71: .PP
72: 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 73: .[
74: gumpSF
75: .]
1.1 snw 76: .SH
77: Early History
78: .PP
1.3 snw 79: 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,
80: .[
1.9 snw 81: walters99
82: %P 19
1.3 snw 83: .]
1.14 ! snw 84: 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 absorbing their technology into their \fIOpen M\fR product, which would later become \fIInterSystems Cache\fR.
1.3 snw 85: .[
1.9 snw 86: ibid
87: %P 18
1.3 snw 88: .]
1.14 ! snw 89: .KS
! 90: .TS
! 91: center tab(#);
! 92: Cb Cb
! 93: L L.
! 94: Implementation#Year
! 95: DataTree MUMPS (DTM)#1993
! 96: Digital Standard MUMPS (DSM)#1995
! 97: .[
! 98: dsmAcquisition
! 99: .]
! 100: Micronetics Standard MUMPS (MSM)#1998
! 101: .TE
! 102: .CD
! 103: .SM
! 104: \fIFigure 1. M implementations absorbed by InterSystems Corp.\fR
! 105: .NL
! 106: .LD
! 107: .KE
1.13 snw 108: 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.
1.3 snw 109: .[
110: freemREADME
111: .]
1.5 snw 112: .KS
1.3 snw 113: .PP
114: 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.
115: .[
116: portSCO
117: .]
118: This port brought support for the \fIscoansi\fR terminal type, including colors and ANSI X3.64 control mnemonics.
1.5 snw 119: .KE
1.1 snw 120: .SH
1.11 snw 121: Generic Universal M Project
1.1 snw 122: .PP
1.5 snw 123: 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 124: .[
125: c2m
126: .]
127: .PP
128: Although the specification for the GUM interface to global handlers attained a reasonably well-specified level of completeness,
129: .[
130: gumapi
131: .]
1.9 snw 132: and Lawrence Landis and others developed a mostly-complete implementation of a GUM global handler,
1.3 snw 133: .[
134: gumpsrc
135: .]
136: none of the other envisioned components were ever completed, and specifically, the interpreter component was missing.
1.1 snw 137: .SH
138: Shalom's Gift
139: .PP
1.5 snw 140: 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 141: .[
142: freemREADME
143: .]
1.1 snw 144: .IP \(bu 2
145: Implement the entirety of \fIANSI X11.1-1995\fR
146: .IP \(bu 2
147: Use Structured System Variables instead of \fIVIEW\fR commands and \fI$VIEW\fR functions
148: .IP \(bu 2
149: Raise the string size limits
150: .IP \(bu 2
151: Implement MWAPI, OMI, X11 bindings, and GKS bindings
152: .IP \(bu 2
153: Be substantially free of major bugs
154: .PP
155: 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 156: .SH
1.7 snw 157: .KS
1.1 snw 158: Merging GUMP and FreeM
159: .PP
1.5 snw 160: 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 161: .[
1.9 snw 162: shortWalters99
163: %P 19
1.3 snw 164: .]
165: 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.
166: .[
167: freemContributors
168: .]
169: The goals of this team were to:
1.1 snw 170: .IP \(bu 2
171: Meet Shalom's requirements for a public release of FreeMUMPS
172: .IP \(bu 2
173: Convert FreeMUMPS into the first interpreter component of the GUMP
1.11 snw 174: .KE
1.1 snw 175: .PP
1.5 snw 176: During this period, Ronald L. Fox of Diagnostic Laboratory Services in Honolulu, HI (who passed in 2010)
1.3 snw 177: .[
178: ronFoxGrave
179: .]
180: ported FreeMUMPS from SCO UNIX to Red Hat 5 and glibc-6.
181: .[
182: ronFoxPort
183: .]
184: Steve "Saintly" Zeck of the U.C. Davis Veterinary Medical Teaching Hospital
185: .[
186: saintlyBio
187: .]
188: also attempted to rewrite the symbol table code to lift string size limits,
189: .[
190: saintlySymtab
191: .]
1.8 snw 192: David Whitten enhanced some of the implementation-specific extensions, and Lawrence Landis integrated Zeck's symbol table work.
1.3 snw 193: .PP
1.5 snw 194: 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 195: .[
196: mdc_implementations
197: .]
198: M implementation.
199: .[
200: Changes.GUM
201: .]
202: Dr. Walters also received the implementation ID of 49 from then secretary of the M Development Committee, Don Piccone.
203: .[
1.9 snw 204: ibid
1.3 snw 205: .]
1.1 snw 206: .PP
1.5 snw 207: 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 208: .[
209: trochaFork
210: .]
1.7 snw 211: .KS
1.1 snw 212: .SH
213: The GT.M Free Software Release
214: .PP
215: 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 216: .[
217: fisSanchezAcquisition
218: .]
219: .PP
220: When GT.M was released under the GNU General Public License in 2000,
221: .[
222: gtmRelease
223: .]
1.5 snw 224: 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 225: .[
226: freem050
227: .]
228: However, Axel Trocha's private port would continue to be developed for some years.
1.7 snw 229: .KE
1.1 snw 230: .SH
231: Axel Trocha's Fork
232: .PP
1.11 snw 233: 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 234: .IP \(bu 2
235: A native port to Microsoft Windows
236: .IP \(bu 2
237: Compiling FreeM as an Apache web server module, allowing FreeM to be used easily for web development
238: .IP \(bu 2
239: 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
240: .IP \(bu 2
241: Extensions allowing FreeM to be used as a command-line shell, along the lines of UNIX \fIbash\fR, Windows \fIcmd.exe\fR, etc.
242: .PP
1.5 snw 243: Trocha also maintains ownership of the \fIfreem.net\fR Internet domain,
1.3 snw 244: .[
245: trochaDomain
246: .]
1.5 snw 247: 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 248: .[
249: elvenRunes
250: .]
1.5 snw 251: 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 252: .SH
253: Resuming Primary Development Branch
254: .PP
255: 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.
256: .SH
257: Taking Maintainership
258: .PP
1.5 snw 259: 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 260: .IP \(bu 2
261: Adding support for proper namespaces, configured through a \fIfreem.conf\fR file, which standardizes routine and global storage locations
262: .IP \(bu 2
263: Adding support for Structured System Variables
264: .IP \(bu 2
265: Adding support for the asynchronous event specification from MDC Type A proposal \fIX11/1998-28\fR
266: .[
267: x119828
268: .]
269: .IP \(bu 2
270: Adding support for constants via the \fICONST\fR keyword
271: .IP \(bu 2
272: Adding a \fIWITH\fR command allowing the specification of an implicit prefix to all subsequent variable references
273: .IP \(bu 2
274: Adding a runtime \fIWATCH\fR command, tracking changes to specified local or global variables
275: .IP \(bu 2
276: Adding an \fIASSERT\fR command, which will fail with an error message if the following expression evaluates \fIfalse\fR
277: .IP \(bu 2
278: Removing the Steve Zeck symbol table implementation\(emwhich was unreliable\(emand reverting to the original implementation
279: .IP \(bu 2
280: Adding support for the GNU \fIreadline\fR library, with persistent command line history and editing
281: .IP \(bu 2
282: Adding REPL-like functionality (in direct mode, any M expression beginning with a number will be prepended with an implicit \fIWRITE\fR)
283: .IP \(bu 2
284: Adding transaction processing
285: .IP \(bu 2
286: Adding \fIKVALUE\fR and \fIKSUBSCRIPTS\fR
287: .IP \(bu 2
288: Preparing to support the \fIM Windowing API\fR (MWAPI)
289: .IP \(bu 2
290: Adding the \fIfmadm\fR command-line utility, for system administration functions
291: .IP \(bu 2
292: Adding support for after-image journaling and forward recovery of globals
1.5 snw 293: .KS
1.3 snw 294: .IP \(bu 2
295: Writing a \fItexinfo\fR manual, from which the HTML manual is derived
296: .IP \(bu 2
297: 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 298:
1.5 snw 299: In addition, the FreeM web site
1.3 snw 300: .[
301: freemWebsite
302: .]
303: was created, to distribute downloads and documentation.
1.5 snw 304: .KE
1.3 snw 305: .SH
306: Future
307: .PP
1.5 snw 308: 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 309: .PP
310: 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.
311: .PP
312: 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.
313: .PP
314: 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.
315: .[
316: whyFreeSoftware
317: .]
1.5 snw 318: .SH
319: Conclusion
320: .PP
1.7 snw 321: 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.
322: .PP
323: 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.
324: .PP
325: 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.
326: .PP
1.11 snw 327: 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 328: .KS
1.5 snw 329: .SH
330: Copyright and License
331: .LP
1.6 snw 332: This document is Copyright \[co] 2025 Serena Willis
1.5 snw 333: .LP
334: Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License,
335: .[
336: gfdl
337: .]
338: 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.
339: .LP
1.14 ! snw 340: \fI$Id: freem_history.ms,v 1.13 2025/04/24 01:31:13 snw Exp $\fR
1.7 snw 341: .KE
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>
![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to freem_history.ms CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [Coherent Logic Development] / papers / freem_history