Compatibility notes
LaiRu Legacy vs the original Lasso 8 binary
The goal is application compatibility, not binary identity.
ConcernOriginal Lasso 8LaiRu Legacy
ImplementationProprietary native server and modulesClean-room Rust interpreter
Language scopeThe original Lasso product lineageLasso 8.6 compatibility, including documented 8.5 behavior
Web integrationLasso Service, connectors, SiteAdminFastCGI behind nginx or another current proxy
State modelSite processes and historical thread managerOne ordered warm worker with a bounded queue
AdministrationSiteAdmin and proprietary registriesFiles, environment, systemd, database grants, and proxy config
ExtensionsLCAPI and vendor connectorsRust implementations where evidence exists; otherwise explicit unavailable diagnostics
Compatibility bugsHistorical behavior, documented and undocumentedDocumented observable behavior first; application fixtures decide edge cases
What applications should expect
Common LDML and LassoScript, request parameters, output encoding, collections, custom tags and types, database actions, sessions, files, XML services, cryptography, mail and network clients, image/PDF operations, and framework conventions have direct runtime implementations and tests.
What operators should expect
There is no SiteAdmin clone and no attempt to imitate the original binary layout. Datasources and secrets belong in protected deployment configuration. nginx owns TLS. systemd owns process lifecycle and isolation. The public application tree remains read-only except for deliberately granted state paths.