miser
|
The Miser Project |
orcmid.github.io>
miser>
oMiser>
0.1.6 2025-09-25T18:31Z |
oMiser is constructed as a software library for use on desktop computers. The library manifests ‹ob› = 〈Ob,Of,Ot〉in a computational interpretation. The obap Universal Computation functions are delivered as oMiser operations.
This topic includes definition of software-library interfaces – the oMiser Application Programming Interface (API) – and the derivation of supporting algorithms for manifestation of ‹ob› through the API and ob-cell data structures. This level of access from a computer program provides a semblance of navigating through the ‹ob› manifestation that is achieved.
Releases of the oMiser software are provided under the dev topic. Development of the software is managed in the GitHub Repository, along with discussions, projects and issues.
There are a number of challenges in having oMiser operate with excellent performance. The primitive operations defined for ‹ob› are not ideal, being very low-level relative to the power available on today’s computers. Fortunately, faithful interpretation of ‹ob› in a computer manifestation can provide important optimizations behind the scenes of the API.
There are two qualities that oMiser shall always preserve: immutability and idealism.
Immutability
The API exposes the Ob domain of ‹ob› as consisting of immutable entities that are always “at hand”, even though there are alterations and accelerations behind the API that improve operation without ever violating immutability of the representation. Accelerators expedite operations behind the scenes. Conservers provide for recovery of computer storage of no-longer reachable ob instances. The design and verification of such optimization techniques is covered here.
Idealism
When oMiser operates in multiple instances, even when coordinated by local or remote connections, there is appearance of there being only one ‹ob› Ob domain being navigated by all of the instances. Flavors of distributed operation will maintain that appearance.
Type Abstraction
It is valuable that every ob has an also-immutable applicative interpretation. This allows attaching computer code to ob representations in order to expedite applicative operation. This is valuable obap acceleration.
Although, interpretations of combinators are type-preserving, there is no obvious oMiser mechanism for introduction of identified types and specialized optimization of type-restricted interpretations through their abstraction. It is not possible to escape ‹ob›.
An important improvement would be a means to identify types and somehow guide introduction of machine-language codes for superior representation of rich type interpretations. There is no means of expressing that using oMiser alone. Exploration of how type abstraction can be supported, along with preservation of idealism, will follow availability of oMiser and oFrugal implementations.
Related Material
This placeholder links to raw materials and notes, including text files. There are considated in folios of documentation on the derivation of the oMiser implementation.
| ID | Status | Started | Topic |
|---|---|---|---|
| oMiser.txt | 0.1.3 2024-01-27 | 2017-07-26 | Conception, Definition, and Implementation Notes (temporary) |
| Technical Notes | undated | 2025-09-10 | Subject-matter notes and work items |
| Folios Catalog | undated | 2025-09-10 | Subordinate Topics Catalog |
Using a GitHub account, discuss Miser Project topics in the Discussion section. Propose improvements and removal of defects in Miser Project documentation and software in the Issues section. There are also relevant projects from time to time. For any security concerns, please consult the project security policy.
|
You are navigating the Miser Project on Github |
created 2024-01-20 by orcmid |