[j3s]

absolutely sick of reading through obviously AI-slopped READMEs. it's your project, take a little pride and tell me why i should like it quickly instead of asking your agent to rattle off a list of features -- it's severely boring & offputting.

[marcingas]

Thanks for feedback. Here's a pre-AI-slopped README https://github.com/nooga/let-go/blob/98c2e2ebf38519bceb4f799...

You can also refer to the HN post itself - it says why I think it's cool.

[jimbokun]

This version is infinitely better.

[j3s]

apologies if i was blunt - readme sloppage is a particular annoyance of mine that is quickly becoming common. i'm not against vibecoding, far from it. but a readme is a part of a project that humans immediately touch - seeing it littered with em-dashes signals carelessness.

i appreciate you taking my feedback with grace.

[rcarmo]

I would like to point out, again, that em dashes are very much used by humans that run macOS or iOS — like in this case.

[isityettime]

Also Linux, where it's easy to configure a compose key to mnemonically type all the Unicode goodies you can think of.

Android's software keyboards generally make it easy, too.

[marcingas]

No worries at all. I understand your point. I'll look into fixing this!

[stingraycharles]

Why did you feel the need to slopify your README? The original version read much, much better.

I genuinely don’t understand why people do this.

[marcingas]

Good question, perhaps I really was just careless. I'll look into fixing the README.

[stingraycharles]

It’s all good. Your project is awesome (and I say this as someone who has done Clojure fulltime for 5 years and nowadays write mostly Go).

[uxcolumbo]

What made you stop using Clojure? Lack of Clojure jobs? Or something else?

[stingraycharles]

Job offer I couldn’t refuse that didn’t have Clojure.

Now I work for a fully remote team, can work anywhere in the world, at any moment I want, leading the data / cloud team for a distributed timeseries database.

Can’t complain. :)

Clojure has had a huge, fundamental impact on my way of approaching software development. I actually came from a Haskell / C++ background, but the way Clojure treats data still has a fundamental impact on how I reason about data, architecture and simplicity.

I did have some issues with how Clojure is managed and do not always subscribe to Rich’s vision (I think core.spec makes no sense, a heavily macro based global state registry is fundamentally not how I would design this, and malli is infinitely better. same for core.async vs manifold), but that is a minor detail in what was a transformative experience for me.

I believe I am not alone when I say this.

I’m still following things from a distance. Considering the current thread, I’m actually very interested in yank, which is Clojure on LLVM, and have been sponsoring that project for a few years. That would be very nice if it could enter stable state, I may take another look again.