jaunt-lang / jaunt

[ABANDONED] A jaunt away from Clojure
https://github.com/jaunt-lang/jaunt/issues/157
134 stars 6 forks source link

Jaunt is dead. What next? #157

Open arrdem opened 7 years ago

arrdem commented 7 years ago

I'm calling it. Jaunt's dead in the water.

There are a variety of reasons for this. I made too many changes. I didn't bake some of them well. Clojure is a very complex code base and I hit a number of walls when I tried to do various things. Things that should have worked didn't for strange reasons.

Ultimately, nobody else (with thanks to @danielcompton) ever really stepped up with ideas about what a "better Clojure" would look like. Despite grousing, the overwhelming majority of Clojure's community seems content with current leadership and direction (or lack thereof). As evidenced now by the bleached bones of Dunaj and Jaunt, there simply isn't a market for a "community" fork although many institutions operate their own internal Clojure forks.

For me, ox-lang/ox is next. It's a clean break. It's easier to work on without getting frustrated at the Clojure core or its various cultural baggage. It fits in my head and is a nice release at the end of the day.

I'd be pleased to hand Jaunt off to other maintainership, and would appreciate feedback on whether it's valuable to the Clojure community to leave this as a cultural artifact / warning to the wise or whether I should just shut it down.

plexus commented 7 years ago

Thanks @arrdem for trying to making things better and challenging the status quo. I'm sorry to see Jaunt go this way, I think simply having these forks to demonstrate alternative ways forward is part of a healthy ecosystem. Good luck with Ox! I'm curious to see where that will go.

One thing I'm curious about: did you have any particular successes with Jaunt? Changes or improvements that really turned out well? Any hard earned lessons for the next person treading this path?

arrdem commented 7 years ago