Mica Alternatives

Similar projects and alternatives to mica

mudmixer

2 0 2.7 JavaScript mica VS mudmixer

MUDMixer is an add-on for MUD clients that enriches the gaming experience with connection mixing functionality and a variety of other features.
moor

7 149 9.7 Rust mica VS moor

A rewrite of the classic LambdaMOO server; but in Rust and on a modern tech stack
InfluxDB

www.influxdata.com featured

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
rmoo

2 8 1.8 Emacs Lisp mica VS rmoo

A major mode for interacting with MOOs.
fastglobal

2 1,126 0.0 Elixir mica VS fastglobal

Fast no copy globals for Elixir & Erlang.
nmoo

1 10 8.2 Nim mica VS nmoo

An enhanced LambdaMOO-like MOO
tinyfugue

1 55 4.9 C mica VS tinyfugue

TinyFugue - Rebirth
EtaMOO

1 35 0.0 Haskell mica VS EtaMOO

A new implementation of the LambdaMOO server
SaaSHub

www.saashub.com featured

SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better mica alternative or higher similarity.

Suggest an alternative to mica

mica reviews and mentions

Posts with mentions or reviews of mica. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-09-23.

Show HN: I rewrote the 1990's LambdaMOO server from scratch
8 projects | news.ycombinator.com | 23 Sep 2023

I've done the "whole new thing" before, too. 20ish years ago, tho I only have a few fragments of what I worked on back then: https://github.com/rdaum/mica being one of them I found on an old drive. Not complete.
But sticking with compatibility has allowed me to enforce development discipline, basically. And then I'll move it onwards from there.
Re: world state / transactions -- yeah, basically all I/O and mutations happen in a transactional context, and then at commit time conflicts are resolved; if they're not resolve-able, the transaction is retried in a new state. As for overhead, yes potentially maybe a lot, but it's also a solvable problem; this is how an MVCC SQL database (like, even Postgres) works. TLDR it's likely inefficient now, but I believe I can make it efficient. And I think it's the best to solve the shared world state problem and still meet user's expectations of consistency.
Re: the MOO client, it's `rmoo.el`: https://github.com/lisdude/rmoo -- it's been around for a long time (25, 30 years?) and it and/or MOO.el (another emacs one) are how/why I learned emacs in the first place. I had to patch my local copy to make it work with emacs 29.1.