What about a lisp that elaborates into Effect flavored typescript?

Very smart and worth a read.

It all converges to lisp in the end

going nuts because no AI app lets you have separate windows per repo/workspace (y'know, like IDEs did for 30 years) plz fix @ claude codex conductor cursor

We should write down the sequence of events for the eventual documentary 🙌

Yo dawg

My thoughts are still evolving, and I do appreciate how crazy this sounds: it started a few months ago with an idea called Open Ontology, my goal was to build a Palantir-like way to model operational ontologies. This turned into a triplestore, kind of similar to event sourcing, but on a attribute/entity/transaction level. I got that working as an Effect library, pluggable storage (sqlite/durable objects/pg/fndb/etc). I then needed a query engine, so I built a datalog engine on top of that triplestore. Then I needed a way to model the actions and mutations and constraints. Then compose those into workflows, then allow users to define views, etc. at some point I realized I wasn't really building a datastore anymore, I was trying to model the operational semantics of an organization, and every layer kept wanting to become declarative (because I am a BIG schema fan). I wanted workflows to be data, then actions to be data, then permissions to be data, then views to be data, then eventually logic itself wanted to be data, just like HttpApi. I could do this with Schema, but if the goal was to embed in markdown, why limit to typescript? The goal is also not authoriing ergonomics, its reading ergonomics. This culminated in the idea of embedded a lisp dsl into markdown, allowing a markdown file to function as both the spec as well as the implementation. Lisp serving as a harness for highly concise dsls. However, it needed HM type checking and built in support for effect and schema modeling. So I set down the path of building a custom lisp to support this concept. I'm currently calling this language Forma. In the end I have the whole system mostly working including LSP and IDE support, terraform style deployments with git / PR like ux, and a runtime to actually run the entire graph. Because it is lisp, it is homoiconic, everything is completely auditable, the data, the actions, the schema, the execution, and the evolution. I can argue Schema is also a Lisp, and could get all the same benefits, but the lisp syntax turned out really clean. I haven't open sourced it yet, because that is a one way door and I don't have a lot of open source experience. Some domains I am playing with: open-ontology.com (thinking a way to share ontology definitions- Employees, Departments, Projects, etc. as a public library of operational ontologies, or modules like Stipe of Salesforce) ontology.run (maybe a hosting service for the above, but not sure yet) forma-lang.com (the lisp dsl for executable declarations, with built in effect and schema modeling, and an elaboration phase for designing custom dsls) meta-effects.com (my attempt to put a name to the primitive, the company behind the above, maybe a consulting / implementation shop for organizations that want to use this technology, tbd) Again, I know this is crazy, and very much an LLM induced psychosis, but I think LLMs should make our ambitions with software much bigger, and this is mine

This is what I am currently spending my llm psychosis tokens on

That's actually good, wow

I fully adopted @EffectTS_ the day typescript fixed the issue forcing an adapter in the gen syntax. We owe a lot to that one PR by @ahejlsberg

Not bad for a one shot

we can support pdf and png correctly in the diff view? @superset_sh

Referring to the Codex App of course