Return to freem_history.ms CVS log

Up to [Coherent Logic Development] / papers / freem_history

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

1.2       snw         1: \"
1.19    ! snw         2: \" $Id: freem_history.ms,v 1.18 2025/04/24 18:54:56 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.19    ! snw         8: \"   Revision 1.18  2025/04/24 18:54:56  snw
        !             9: \"   Updates
        !            10: \"
1.18      snw        11: \"   Revision 1.17  2025/04/24 18:46:33  snw
                     12: \"   Clean up refs and add ackowledgments
                     13: \"
1.17      snw        14: \"   Revision 1.16  2025/04/24 17:07:50  snw
                     15: \"   Updates
                     16: \"
1.16      snw        17: \"   Revision 1.15  2025/04/24 16:47:58  snw
                     18: \"   Reorganize document, add MUMPS language overview
                     19: \"
1.15      snw        20: \"   Revision 1.14  2025/04/24 15:33:29  snw
                     21: \"   Add table of ISC-acquired M implementations
                     22: \"
1.14      snw        23: \"   Revision 1.13  2025/04/24 01:31:13  snw
                     24: \"   Add biblio checker
                     25: \"
1.13      snw        26: \"   Revision 1.12  2025/04/23 18:59:53  snw
                     27: \"   Refine wording
                     28: \"
1.12      snw        29: \"   Revision 1.11  2025/04/23 18:58:31  snw
                     30: \"   Refine awkward paragraphing
                     31: \"
1.11      snw        32: \"   Revision 1.10  2025/04/23 18:44:26  snw
                     33: \"   Correct capitalization error in abstract
                     34: \"
1.10      snw        35: \"   Revision 1.9  2025/04/23 18:40:00  snw
                     36: \"   Improve footnotes
                     37: \"
1.9       snw        38: \"   Revision 1.8  2025/04/23 15:12:13  snw
                     39: \"   Improve wording
                     40: \"
1.8       snw        41: \"   Revision 1.7  2025/04/23 15:05:45  snw
                     42: \"   Fix typographical problems
                     43: \"
1.7       snw        44: \"   Revision 1.6  2025/04/23 13:32:34  snw
                     45: \"   Fix copyright symbol
                     46: \"
1.6       snw        47: \"   Revision 1.5  2025/04/23 13:29:37  snw
                     48: \"   Add copyright and license, shorten URLs
                     49: \"
1.5       snw        50: \"   Revision 1.4  2025/04/22 18:16:06  snw
                     51: \"   Remove references to FreeM as a database
                     52: \"
1.4       snw        53: \"   Revision 1.3  2025/04/22 17:54:09  snw
                     54: \"   Initial draft of FreeM History paper
                     55: \"
1.3       snw        56: \"   Revision 1.2  2025/04/22 14:56:22  snw
                     57: \"   Add comment header to FreeM History
1.2       snw        58: \"
1.3       snw        59: \"
                     60: .R1
                     61: database ../references.bib
                     62: move-punctuation
                     63: .R2
1.1       snw        64: .TL
                     65: The History of FreeM
                     66: .AU
                     67: Serena Willis
                     68: .AI
                     69: Coherent Logic Development
                     70: .AB
1.19    ! snw        71: The history of M, as well as the specifics of FreeM\(emthe implementation maintained by the author for the last decade\(emare extensive and complex topics. Here, we will present an overview of the M language and its history in general, proceeding thence specifically to the historical background and development of FreeM itself, as well as its current status and goals. Though publicly-available information is sparse, efforts have been made to cite as many sources\u\s-3*\s+3\d as possible.
1.17      snw        72: .FS *
                     73: Note that all world wide web sources have had their URLs shortened for readability. Following these URLs will automatically redirect the reader to the appropriate, original source. All such URLs were accessed by the author between 22 and 24 April 2025.
                     74: .FE
1.1       snw        75: .AE
1.17      snw        76: .NH
1.19    ! snw        77: M LANGUAGE OVERVIEW
1.1       snw        78: .PP
1.15      snw        79: \fIMUMPS\fR\(emnow generally referred to as \fIM\fR to distance it from the infectious disease\(emis an imperative, general-purpose, command-oriented programming language supporting persistent, hierarchical, sparse arrays. It includes high-level support for multi-user, multi-processing applications with flexible concurrency control.
1.1       snw        80: .PP
1.15      snw        81: MUMPS, being an acronym for \fIM\fRassachusetts General Hospital \fIU\fRtility \fIM\fRulti-\fIP\fRrogramming \fIS\fRystem, was developed by Neil Pappalardo, Robert A. Greenes, and Curt Marble of Dr. Octo Barnett's lab at Massachusetts General Hospital in 1966-1967.
1.3       snw        82: .[
1.15      snw        83: greenes1969
1.3       snw        84: .]
1.15      snw        85: Inspired by RAND Corporation's JOSS, and the TELCOMP and STRINGCOMP languages from Bolt, Beranek and Newman, MUMPS' earliest and most prominent use cases were in the field of health informatics.
1.3       snw        86: .[
1.15      snw        87: greenes1970
1.3       snw        88: .]
                     89: .[
1.15      snw        90: pendergrass1969
1.3       snw        91: .]
1.15      snw        92: .PP
                     93: MUMPS code is divided into program units referred to as \fIroutines\fR, which are roughly analagous to \fImodules\fR or \fIcompilation units\fR in more mainstream languages. Routines are then further divided into labels (or \fItags\fR in MUMPS parlance), which serve as entry points into the routine. Subroutines and functions (the latter known as \fIextrinsic functions\fR) are introduced as tags with an optional, parenthesized \fIformallist\fR, being a list of parameters expected by the subroutine or extrinsic function.
                     94: .PP
                     95: Perhaps the most unique feature of M, the \fIglobal\fR, is a persistent, hierarchical, sparse array allowing developers to easily implement database features directly in the application's primary development language:
                     96: .IP
                     97: .DS L
                     98: .ft C
                     99: ROUTINE ;
                    100:   SET ^PEOPLE("Willis, Serena","DOB")="1980-12-01"
                    101:   SET ^PEOPLE("Willis, Serena","SEX")="F"
                    102:   SET ^PEOPLE("Willis, Serena","COUNTRY")="US" 
                    103: .ft
                    104: .PP
                    105: The above routine would be called with \fIDO ^ROUTINE\fR, resulting in a data structure in fixed storage where the elements (known in M parlance as \fIsubscripts\fR), i.e., \fI"Willis, Serena"\fR, are automatically sorted on insertion, allowing for rapid retrieval. Rough analogues can be found in the \fIPICK\fR operating system, as well as BBN \fIFILECOMP\fR, the latter of which was a direct influence in the early development of M.
                    106: .KS
                    107: .PP
                    108: Early versions of M included \fIMGH MUMPS\fR from Massachusetts General Hospital, and \fIDigital Standard MUMPS\fR from Digital Equipment Corporation. Notably, early commercial versions of M were commercial software, somewhat limiting the language's spread outside of its ecological niche of health informatics.
1.16      snw       109: .TS
                    110: center tab(#);
                    111: Cb Cb
                    112: L L.
                    113: Vendor#Implementation
                    114: Mass. General Hospital#MGH MUMPS
                    115: Digital Equipment Corp.#Digital Standard MUMPS (DSM)
                    116: InterSystems Corp.#InterSystems Standard MUMPS (ISM), Open M, Cache, IRIS Data Platform
                    117: Data Tree#Data Tree MUMPS (DTM)
                    118: Micronetics#Micronetics Standard MUMPS (MSM)
                    119: Patterson & Gray#PSM-11, PSM-32, PSM-V
                    120: MGlobal International Inc.#CCSM, MacMUMPS, M Global MUMPS, M3 Lite
                    121: U.C. Davis#MicroMUMPS
                    122: Ray Newman#MUMPS V1
                    123: Fourth Watch Software LC#Reference Standard M (RSM)
                    124: Kevin O'Kane#Mumps-II, Open Mumps, GPL Mumps
                    125: M21 Ltd.#M21
                    126: Fidelity National Information Services#GT.M (Greystone Technology MUMPS)
                    127: YottaDB#YottaDB
                    128: Eugene Karataev#MiniM
                    129: .TE
                    130: .CD
                    131: .SM
                    132: \fIFigure 1. Partial list of M implementations.\fR
                    133: .NL
                    134: .LD
1.15      snw       135: .KE
1.17      snw       136: .NH
                    137: EARLY HISTORY OF FREEM
1.1       snw       138: .PP
1.3       snw       139: 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,
                    140: .[
1.9       snw       141: walters99
                    142: %P 19
1.3       snw       143: .]
1.14      snw       144: 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       145: .[
1.9       snw       146: ibid
                    147: %P 18
1.3       snw       148: .]
1.14      snw       149: .KS
                    150: .TS
                    151: center tab(#);
                    152: Cb Cb
                    153: L L.
                    154: Implementation#Year
                    155: DataTree MUMPS (DTM)#1993
                    156: Digital Standard MUMPS (DSM)#1995
                    157: .[
                    158: dsmAcquisition
                    159: .]
                    160: Micronetics Standard MUMPS (MSM)#1998
                    161: .TE
                    162: .CD
                    163: .SM
1.16      snw       164: \fIFigure 2. M implementations absorbed by InterSystems Corp.\fR
1.14      snw       165: .NL
                    166: .LD
                    167: .KE
1.15      snw       168: .PP
1.13      snw       169: 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       170: .[
                    171: freemREADME
                    172: .]
1.5       snw       173: .KS
1.3       snw       174: .PP
                    175: 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.
                    176: .[
                    177: portSCO
                    178: .]
                    179: This port brought support for the \fIscoansi\fR terminal type, including colors and ANSI X3.64 control mnemonics.
1.5       snw       180: .KE
1.17      snw       181: .NH
                    182: INITIAL INVOLVEMENT
1.15      snw       183: .PP
                    184: 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.
                    185: .PP
                    186: Mr. Landis was the owner of FreeM's SourceForge repository
                    187: .[
                    188: gumpSF
                    189: .]
                    190: , 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 \fImumpster.org\fR forums.
                    191: .[
                    192: freem014
                    193: .]
                    194: .PP
                    195: In 2014, Mr. Landis gave the author administrator access to the FreeM SourceForge repository and transferred maintainership of the project to her.
                    196: .[
                    197: gumpSF
                    198: .]
1.17      snw       199: .NH
                    200: GENERIC UNIVERSAL M PROJECT
1.1       snw       201: .PP
1.5       snw       202: 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       203: .[
                    204: c2m
                    205: .]
                    206: .PP
                    207: Although the specification for the GUM interface to global handlers attained a reasonably well-specified level of completeness,
                    208: .[
                    209: gumapi
                    210: .]
1.9       snw       211: and Lawrence Landis and others developed a mostly-complete implementation of a GUM global handler,
1.3       snw       212: .[
                    213: gumpsrc
                    214: .]
                    215: none of the other envisioned components were ever completed, and specifically, the interpreter component was missing.
1.17      snw       216: .NH
                    217: FREEM DONATED TO MUG DEUTSCHLAND
1.1       snw       218: .PP
1.5       snw       219: 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       220: .[
                    221: freemREADME
                    222: .]
1.1       snw       223: .IP \(bu 2
                    224: Implement the entirety of \fIANSI X11.1-1995\fR
                    225: .IP \(bu 2
                    226: Use Structured System Variables instead of \fIVIEW\fR commands and \fI$VIEW\fR functions
                    227: .IP \(bu 2
                    228: Raise the string size limits
                    229: .IP \(bu 2
                    230: Implement MWAPI, OMI, X11 bindings, and GKS bindings
                    231: .IP \(bu 2
                    232: Be substantially free of major bugs
                    233: .PP
                    234: 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.17      snw       235: .NH
                    236: MERGING GUMP AND FREEM
1.1       snw       237: .PP
1.5       snw       238: 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       239: .[
1.9       snw       240: shortWalters99
                    241: %P 19
1.3       snw       242: .]
                    243: 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.
                    244: .[
                    245: freemContributors
                    246: .]
                    247: The goals of this team were to:
1.1       snw       248: .IP \(bu 2
                    249: Meet Shalom's requirements for a public release of FreeMUMPS
                    250: .IP \(bu 2
                    251: Convert FreeMUMPS into the first interpreter component of the GUMP
                    252: .PP
1.5       snw       253: During this period, Ronald L. Fox of Diagnostic Laboratory Services in Honolulu, HI (who passed in 2010)
1.3       snw       254: .[
                    255: ronFoxGrave
                    256: .]
                    257: ported FreeMUMPS from SCO UNIX to Red Hat 5 and glibc-6.
                    258: .[
                    259: ronFoxPort
                    260: .]
                    261: Steve "Saintly" Zeck of the U.C. Davis Veterinary Medical Teaching Hospital
                    262: .[
                    263: saintlyBio
                    264: .]
                    265: also attempted to rewrite the symbol table code to lift string size limits,
                    266: .[
                    267: saintlySymtab
                    268: .]
1.8       snw       269: David Whitten enhanced some of the implementation-specific extensions, and Lawrence Landis integrated Zeck's symbol table work.
1.3       snw       270: .PP
1.5       snw       271: 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       272: .[
1.18      snw       273: m_implementations
1.3       snw       274: .]
                    275: M implementation.
                    276: .[
                    277: Changes.GUM
                    278: .]
                    279: Dr. Walters also received the implementation ID of 49 from then secretary of the M Development Committee, Don Piccone.
                    280: .[
1.9       snw       281: ibid
1.3       snw       282: .]
1.1       snw       283: .PP
1.5       snw       284: 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       285: .[
                    286: trochaFork
                    287: .]
1.17      snw       288: .NH
                    289: GT.M RELEASED AS FREE SOFTWARE
1.1       snw       290: .PP
                    291: 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       292: .[
                    293: fisSanchezAcquisition
                    294: .]
1.18      snw       295: .KS
1.3       snw       296: .PP
                    297: When GT.M was released under the GNU General Public License in 2000,
                    298: .[
                    299: gtmRelease
                    300: .]
1.5       snw       301: 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       302: .[
                    303: freem050
                    304: .]
                    305: However, Axel Trocha's private port would continue to be developed for some years.
1.7       snw       306: .KE
1.17      snw       307: .NH
                    308: FORKED BY AXEL TROCHA
1.1       snw       309: .PP
1.11      snw       310: 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       311: .IP \(bu 2
                    312: A native port to Microsoft Windows
                    313: .IP \(bu 2
                    314: Compiling FreeM as an Apache web server module, allowing FreeM to be used easily for web development
                    315: .IP \(bu 2
                    316: 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
                    317: .IP \(bu 2
                    318: Extensions allowing FreeM to be used as a command-line shell, along the lines of UNIX \fIbash\fR, Windows \fIcmd.exe\fR, etc.
                    319: .PP
1.5       snw       320: Trocha also maintains ownership of the \fIfreem.net\fR Internet domain,
1.3       snw       321: .[
                    322: trochaDomain
                    323: .]
1.15      snw       324: 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 \fIElven Runes\fR website.
1.3       snw       325: .[
                    326: elvenRunes
                    327: .]
1.5       snw       328: 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.17      snw       329: .NH
                    330: RESUMING PRIMARY DEVELOPMENT
1.1       snw       331: .PP
                    332: 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.
1.17      snw       333: .NH
                    334: TAKING MAINTAINERSHIP
1.1       snw       335: .PP
1.5       snw       336: 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       337: .IP \(bu 2
                    338: Adding support for proper namespaces, configured through a \fIfreem.conf\fR file, which standardizes routine and global storage locations
                    339: .IP \(bu 2
                    340: Adding support for Structured System Variables
                    341: .IP \(bu 2
                    342: Adding support for the asynchronous event specification from MDC Type A proposal \fIX11/1998-28\fR
                    343: .[
                    344: x119828
                    345: .]
                    346: .IP \(bu 2
                    347: Adding support for constants via the \fICONST\fR keyword
                    348: .IP \(bu 2
                    349: Adding a \fIWITH\fR command allowing the specification of an implicit prefix to all subsequent variable references
                    350: .IP \(bu 2
                    351: Adding a runtime \fIWATCH\fR command, tracking changes to specified local or global variables
                    352: .IP \(bu 2
                    353: Adding an \fIASSERT\fR command, which will fail with an error message if the following expression evaluates \fIfalse\fR
                    354: .IP \(bu 2
                    355: Removing the Steve Zeck symbol table implementation\(emwhich was unreliable\(emand reverting to the original implementation
                    356: .IP \(bu 2
                    357: Adding support for the GNU \fIreadline\fR library, with persistent command line history and editing
                    358: .IP \(bu 2
                    359: Adding REPL-like functionality (in direct mode, any M expression beginning with a number will be prepended with an implicit \fIWRITE\fR)
                    360: .IP \(bu 2
                    361: Adding transaction processing
                    362: .IP \(bu 2
                    363: Adding \fIKVALUE\fR and \fIKSUBSCRIPTS\fR
                    364: .IP \(bu 2
                    365: Preparing to support the \fIM Windowing API\fR (MWAPI)
                    366: .IP \(bu 2
                    367: Adding the \fIfmadm\fR command-line utility, for system administration functions
                    368: .IP \(bu 2
                    369: Adding support for after-image journaling and forward recovery of globals
1.5       snw       370: .KS
1.3       snw       371: .IP \(bu 2
                    372: Writing a \fItexinfo\fR manual, from which the HTML manual is derived
                    373: .IP \(bu 2
                    374: 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       375: 
1.5       snw       376: In addition, the FreeM web site
1.3       snw       377: .[
                    378: freemWebsite
                    379: .]
                    380: was created, to distribute downloads and documentation.
1.5       snw       381: .KE
1.17      snw       382: .NH
                    383: FUTURE
1.3       snw       384: .PP
1.5       snw       385: 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       386: .PP
                    387: 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.
                    388: .PP
                    389: 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.
                    390: .PP
                    391: 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.
                    392: .[
                    393: whyFreeSoftware
                    394: .]
1.17      snw       395: .NH
                    396: CONCLUSION
1.5       snw       397: .PP
1.7       snw       398: 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.
                    399: .PP
                    400: 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.
                    401: .PP
                    402: 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.
                    403: .PP
1.11      snw       404: 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.18      snw       405: .KS
1.17      snw       406: .NH
                    407: ACKNOWLEDGMENTS
                    408: .PP
                    409: Certainly, the intellects responsible for giving us M are too numerous to mention by name, but their importance cannot be overstated. The author would like to especially credit Lawrence Landis for his early and innumerable contributions to her development, both generally as a practitioner of software development, and specifically for introducing her to the M programming language, and inculcating in her a love of exploration and innovation.
                    410: .PP
                    411: Thanks are due also to David Wicksell, for countless hours of collaboration on FreeM spanning more than a decade, and for providing ideas and inspiration.
                    412: .PP
                    413: I would also like to thank Ken McGlothlen of Vista Expertise Network for his efforts in editing multiple drafts of this paper.
                    414: .PP
1.18      snw       415: Finally, to my wife, Miriam\(ema brilliant technologist in her own right\(emand daughters, without whose inestimable patience and understanding as the author buries herself in countless passion projects, such projects would not be possible.
                    416: .KE
1.7       snw       417: .KS
1.17      snw       418: .NH
                    419: COPYRIGHT AND LICENSE
1.5       snw       420: .LP
1.6       snw       421: This document is Copyright \[co] 2025 Serena Willis
1.5       snw       422: .LP
                    423: Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License,
                    424: .[
                    425: gfdl
                    426: .]
                    427: 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. 
                    428: .LP
1.19    ! snw       429: \fI$Id: freem_history.ms,v 1.18 2025/04/24 18:54:56 snw Exp $\fR
1.7       snw       430: .KE