We have enough discussion of UNIX brain damage here, so it's high time for a real change. Multix II is a programmer-friendly distributed Functional OS topology. This enables extreme-Agile teams to introduce AI-driven LEAN software JIT composition, collaboration, live interactivity, language mixing, multi-layered coding surfaces and other advanced Dev, Test and DevOps technologies. You can now have effective use of AI-automation within your PLM & SDLC processes, significantly improving productivity.
To all your weenies out there who don't immediately grasp the significance of this, I'll explain. Multix II is a Functional OS inspired by Multics with a HTML user interface using Rho Calculus where the operating system is the monad. It makes heavy use of Applied Category Theory, Persistent Memory, Single Level Memory, and is 100% free of UNIX brain damage as it is developed by NYC bankers and Estonians instead of lambda calculus-addicted East Coast Silicon Valley weenies. It also takes inspiration from blockchain, relational database, and spreadsheet technology, advances that weenies have been slow to understand the true significance of.
https://www.codecraft.ai/
https://medium.com/@reinman
https://twitter.com/datacountry_ai
Operating Systems Need an Overhaul
Functions should be first-class objects for starters. Another is direct
Kleisli support for JSON within the shell. Or how about support for
Kleisli joins and workflow? Handling continuations (lazy eval) at the
filesystem level? On the productivity side, Kan extensions should
handle much of the busy work of scaling out DevOps without having
to rip up code. The system should be able to split out lambdas
automatically at runtime. The list goes on and on.
In other words, Yoneda.
Yeah we know it is all madness drugs etc. to daring to challenge the
Big Tech status quo and take the industry forward into the future.
Category theory has always been controversial for this reason.
Some ideas are out of this world.