9 comments

  • j3s 40 minutes ago
    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 19 minutes ago
      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.

      • stingraycharles 4 minutes ago
        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 2 minutes ago
          Good question, perhaps I really was just careless. I'll look into fixing the README.
      • j3s 9 minutes ago
        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.

        • marcingas 1 minute ago
          No worries at all. I understand your point. I'll look into fixing this!
  • ingy 2 hours ago
    Try out this Wasm browser REPL https://gloathub.org/repl/

    Gloat is a Glojure AOT automation tool. I worked with James Hamlin to get Glojure AOT going last summer and have been moving it forward since. I've also been working with marcingas (nooga) to get Gloat/Glojure/let-go all cooperating.

  • bjconlan 2 hours ago
    This is the kind of clojure port that I always was looking for. Mostly because I thought go's core library and channels abstractions hits a simpler/nicer base API which would with the core & async apis (not to mention scratches my big beautiful binary itch)

    Thanks for your work will definitely check it out again once I get over renewed love for cpp (26)

    Edit how did glojure go under my radar also a great project from the looks

    • giancarlostoro 2 hours ago
      I have played with the idea of making a “old school PHP” style DSL that takes advantage of the Go runtime and packages under the cover. I say old school PHP because PHP used to be a web focused DSL its no longer the case, I feel like it would make for an interesting easy to use backend language similar to PHP but with the full power of Go behind it. Clojure is an excellent choice.
    • marcingas 2 hours ago
      Thanks for kind words! Please don't forget to drop me an issue or two when you eventually get to it :)
  • chr15m 1 hour ago
  • dmitrygr 3 hours ago
    You should see how fast libc gets mmaped() into the VM and the first instr runs :)
    • marcingas 2 hours ago
      Sure, I should clarify: The 7ms here is measured at the point where let-go starts executing user code. It takes 7ms to initialize the compiler, load all stdlib namespaces and compute all vars. So it's not "time to first instruction", it's "time to running your code".
  • brazukadev 2 hours ago
    do you know about Glojure?

    https://github.com/glojurelang/glojure

  • asdfasd323f 2 hours ago
    obviously vibecoded
    • marcingas 2 hours ago
      Yes, I have used AI to boost Clojure compat and fill out some blanks but the runtime itself is not vibecoded. I wrote it myself between Jan 2021 and July 2023. All commits on GH.
    • jeremyjh 1 hour ago
      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.
      • marcingas 42 minutes ago
        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.
      • asdfasd323f 1 hour ago
        I did. And it looks like you did too. Which is why you answered your own question in the second half of your comment, quite amusingly. "Probably" LOL!
        • jeremyjh 42 minutes ago
          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,

    • adi_kurian 1 hour ago
      Is it bad? Did you try it?
      • asdfasd323f 1 hour ago
        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.
        • marcingas 53 minutes ago
          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?
    • blanched 1 hour ago
      You made an account just to post this low effort “criticism”? What’s the point?
      • asdfasd323f 1 hour ago
        You seem personally upset, did you help vibecode this project too?

        No reply. What a low effort objection from you.