Clojure has a dirty little secret

Maybe. I just think that as time went on, the issues became less technical and more about style and standards. And because there was always just one overwhelming voice, most of the ‘minnows’ that got in the way pretty much went their own way.

@teodorlu

I would love it if there were a fork of the language to feature a stripped-down, easily parsable, easily portable subset of the language. ie: no reader macros, no stm, no agents, no transducers, no protocols, no :: keywords.

Basically, a standard to define an immutable lisp without all the fancier clojure features.

I’d love it if there was something similar to the SRFI - where features are grouped and can be optionally added by the implementer on their own platform. So that some or all of those features can then be added back in.

Then, there could be a runtime running on wasm through intermediary language like c.

There’s already a bunch of work done already with experimental clojure implementations on other platforms. What would be really great is if someone can do a survey of what’s out there, group these implementations by features and come up with this minimum subset.

Maybe then when a document has been drawn up, the community can convince those implementers that it’ll be worthwhile to change their code a little to conform to that standard.

I dunno. It’s a lot of work. But to me, it’d definitely be worth it if we will be able to get a optional-gc clojure that we can repl into.