Live data from Hacker News

Show HN: I made a Clojure-like language in Go, boots in 7ms

github.com

21–30 of 106 posts

Re: Show HN: I made a Clojure-like language in Go, boots in 7ms

#21

[flagged]

Did you even look at the repo history? Clearly it blasted off this year that way but that isn't how it started. Probably he got way more into it once he could make faster progress on all the yak shaving required to make it more useful.

Re: Show HN: I made a Clojure-like language in Go, boots in 7ms

#23

The readme clearly has abundant emdashes and emojis everywhere, the code itself is obviously vibed. Not really sure what you're objecting to, to be honest.

Yeah, it has em dashes alright. But the emojis you're referring to were committed in January 2023 (0c4925c). But that's besides the point I guess. What is your point?

Re: Show HN: I made a Clojure-like language in Go, boots in 7ms

#24

[flagged]

Did you even look at the repo history? Clearly it blasted off this year that way but that isn't how it started. Probably he got way more into it once he could make faster progress on all the yak shaving required to make it more useful.

Yeah, pretty much. I abandoned it in 2023 due to lack of time. At this point it had enough lift for solving AoC problems and writing small scripts. I've recently dusted it off and did the boring parts of the "roadmap" with Claude.

Re: Show HN: I made a Clojure-like language in Go, boots in 7ms

#25

[flagged]

So...you didn't ?

https://github.com/nooga/let-go/tree/d9dc094822b2983ebf44604...

In 2023 he had a working Clojure compiler with:

Macros with syntax quote, Reader conditionals, Destructuring, Multi-arity functions, Atoms, channels & go-blocks a'la core.async, Regular expressions (the Go flavor), Simple json, http and os namespaces, Many functions ported from clojure.core, REPL with syntax-highlighting and completions, Simple nREPL server that seems to work with BetterThanTomorrow/calva,

Re: Show HN: I made a Clojure-like language in Go, boots in 7ms

#27
post #26

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.

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.

Re: Show HN: I made a Clojure-like language in Go, boots in 7ms

#28
post #26

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.

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.

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.

Re: Show HN: I made a Clojure-like language in Go, boots in 7ms

#29
post #26

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.

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.

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.

Re: Show HN: I made a Clojure-like language in Go, boots in 7ms

#30

Earlier quoted context omitted.

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.

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.

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