Hacker News Reader

There are binaries for Mac here:

https://codeberg.org/GramEditor/gram/releases/tag/1.0.0

The binary release for Linux is a bit rough, there's an `install.sh` script in the repo which can install the tarball for you. For the next release there will be flatpaks, .deb and .rpm available.

krigon X offices raided in France as UK opens fresh investigation into Grok

Those images are generated from a training set, and it is already well known and reported that those training sets contain _real_ CSAM, real violence, real abuse. That "generated" face of a child is based on real images of real children.

krigon Anthropic acquires Bun

I just reported the bug, it was the bot that was proudly mentioned in the announcement which created the PR and the code...

krigon Anthropic acquires Bun

Right, this is accurate. Except I thought taylordotfish worked for bun, so I guess no one at bun has looked at it at all then.

krigon Anthropic acquires Bun

> Bun, Zig, and uWebsockets are passion projects run by individuals with deep systems programming expertise. furthest thing from vibe coding imaginable.

Sure, I definitely will not throw projects like Zig into that bucket, and I don't actually think Bun is vibe-coded. At least that _used_ to be true, we'll see I guess...

Don't read a snarky comment so literally ;)

krigon Anthropic acquires Bun

> Prior to Bun, there was little focus on performance.

This is just completely insane. We went through more than a decade of performance competition in the JS VM space, and the _only_ justification that Google had for creating V8 was performance.

> The V8 engine was first introduced by Google in 2008, coinciding with the launch of the Google Chrome web browser. At the time, web applications were becoming increasingly complex, and there was a growing need for a faster, more efficient JavaScript engine. Google recognized this need and set out to create an engine that could significantly improve JavaScript performance.

I guess this is the time we live in. Vibe-coded projects get bought by vibe-coded companies and are congratulated in vibe-coded comments.

krigon Anthropic acquires Bun

This announcement made me check in on the arbitrary code execution bug I reported that the Bun Claude bot created a PR for about 3 weeks ago:

https://github.com/oven-sh/bun/pull/24578

So far, someone from the bun team has left a bunch of comments like

> Poor quality code

...and all the tests still seem to be failing. I looked through the code that the bot had generated and to me (who to be fair is not familiar with the bun codebase) it looks like total dogshit.

But hey, maybe it'll get there eventually. I don't envy "taylordotfish" and the other bot-herders working at Oven though, and I hope they get a nice payout as part of this sale.

krigon Lisp interpreter with GC in <750 lines of Odin (and <500 lines of C)

I’ll remove even more and _still_ call it a lisp and there is nothing you can do to stop me.

Any memory management solution will run out of space and terminate unless there is literally infinite memory available.

But I guess hash tables is what people think about when thinking about what makes something a lisp or not.

krigon Lisp interpreter with GC in <750 lines of Odin (and <500 lines of C)

What in the world... jibal was the one who called _me_ a troll, I never called anyone a troll. Lord knows what is happening in this comment section at this point.

krigon Lisp interpreter with GC in <750 lines of Odin (and <500 lines of C)

I can't reply to the reply to this one (guess the thread is getting too deep), but I just wanted to clarify that I'm not a rust critic, I use rust, I like rust, I have no problem with rust. OK great, moving on...

krigon Lisp interpreter with GC in <750 lines of Odin (and <500 lines of C)

I used the word "childish" to describe posting comments about someones personality without any references or examples, and here you are doing the same but adding Gemini to the mix... and I'm the troll? :)

krigon Lisp interpreter with GC in <750 lines of Odin (and <500 lines of C)

Is that really the whole reason for this grudge? He gave you a bunch of comments to work from! I was expecting a lot less from your description.

I don't find it too hard to figure out what he meant - he doesn't want to you change the case style of procedure calls, but he _does_ want you to remove redundant namespacing as in the CURL prefix.

Maybe you could have looked at some other vendored libraries to see how they handled things like constant naming and other formatting?

krigon Lisp interpreter with GC in <750 lines of Odin (and <500 lines of C)

I'm offended by the Gemini slop!

krigon Lisp interpreter with GC in <750 lines of Odin (and <500 lines of C)

That's the nice thing about a little side project, I can just have fun and noodle away at it without worrying about safety or comments ;)

krigon Lisp interpreter with GC in <750 lines of Odin (and <500 lines of C)

Dude, I find it utterly offensive that you and the other guy keep referring to all these interactions with Bill where he was a mean boy, and yet the closest to an actual quote or reference is some Gemini slop? If you're going to be that lazy, it would be easier to not post anything at all.

https://anthonymoser.github.io/writing/ai/haterdom/2025/08/2...

krigon Lisp interpreter with GC in <750 lines of Odin (and <500 lines of C)

First, no it isn't. What baseless accusation did I make?

I haven't seen the conversations he is referring to, he didn't link to or quote anything. It's just some general complaint about Bill, which may be true but who cares?

krigon Lisp interpreter with GC in <750 lines of Odin (and <500 lines of C)

I don't really get the distinction between adding the dynamic-literals feature flag and using unsafe in Rust? Like, if he had called it #+unsafe dynamic-literals, would that have been better?

krigon Lisp interpreter with GC in <750 lines of Odin (and <500 lines of C)

Well, first of all, I guess I am wrong! Hey, I'm not Bill, just a user of the language.

A couple of clarifications, though: I did mean unsafe rust, not the safe subset. No need to get rude!

Second of all, I am of course not under the illusion that Odin prevents use-after-free (and thus, technically, it does allow UB I guess). I just don't think Bill is either. So clearly he doesn't mean UB by the same definition as you do.

_My_ use of UB has always been in the context of what a compiler will do during optimization, and the discussion I've seen in the context of C compilers is that they perform optimizations that remove code or change code in surprising ways because the way the code was written technically resulted in UB. But I'm neither a spec writer or a compiler author, so I don't really care that much about the actual definition of the term.

Anyway, best of luck in convincing Bill to use the term correctly as well! I won't mention UB when talking about the benefits of Odin in the future. :)

krigon Lisp interpreter with GC in <750 lines of Odin (and <500 lines of C)

I'm not the one throwing baseless accusations around.

"He was mean to me once" isn't that interesting, especially without anything concrete to back it up.

krigon Lisp interpreter with GC in <750 lines of Odin (and <500 lines of C)

Well, the statement is circular, colloquial speech doesn't have to be coherent. It's my understanding of what people generally mean when they complain about UB in the C standard, and it seems to be what gingerbill means too.

My take on what he is saying is that the odin compiler won't try to exploit that there is some behavior which is platform-defined or only knowable at runtime to do aggressive optimizations etc.

https://xcancel.com/TheGingerBill/status/1495004577531367425

To point out that use after free is possible in Odin is not really a gotcha unless you really are just arguing semantics. That's by design, just like use after free is possible in C or C++ or Rust too.

krigon Lisp interpreter with GC in <750 lines of Odin (and <500 lines of C)

This is super cool!

I could imagine writing a very basic forth or lisp compiler in assembler, but even that would be quite the project.

krigon Lisp interpreter with GC in <750 lines of Odin (and <500 lines of C)

Some day I might write a walkthrough of it, but it’s just a toy really.

krigon Lisp interpreter with GC in <750 lines of Odin (and <500 lines of C)

I don’t think he works for me. I am not paying him. To the contrary, if anything _I_ am in debt since I am using all this code that he put out there for free.

I guess there are a few things I could do in that situation. Move on to something else, try to figure out why he didn’t like it on my own, fork the language if it’s big enough and important enough to me.

But yeah, maybe he is busy? Maybe he thinks you are capable of working it out yourself?

Not to be too harsh about it, but yeah, that’s just the way it is sometimes. Maybe he was having a bad day, that happens to people.

krigon Lisp interpreter with GC in <750 lines of Odin (and <500 lines of C)

Well, sure. If that’s what you mean by having UB then it’s trivially true for any language with a C FFI for example, or rust with unsafe. I guess what I consider UB is when the compiler exploits UB for optimizations, like discarding code that could invoke UB, which as far as I know odin doesn’t do.

krigon Lisp interpreter with GC in <750 lines of Odin (and <500 lines of C)

> Me too. I am just not going to contribute. No big deal.

Makes sense! Plenty of other languages and projects out there.

krigon Lisp interpreter with GC in <750 lines of Odin (and <500 lines of C)

Sorry to hear that! I haven’t had any such experience, quite the opposite.

But I’m also an old. If someone tells me my code is shit, 1) they are probably right, and 2) I don’t really care. I can probably look at their code and find flaws in it.

In the end, Odin is Bills project and he decides what goes into it, I’m fine with that.

krigon Lisp interpreter with GC in <750 lines of Odin (and <500 lines of C)

Well, without concrete examples this just sounds childish TBH.

But I haven’t looked very closely at it myself, hence the afaik qualifier.

krigon Lisp interpreter with GC in <750 lines of Odin (and <500 lines of C)

First off, you wouldn’t write an actual interpreter for lisp like this if you wanted to use it for anything serious, it’s very slow.

The parser is very simple thanks to the s-expressions, and the only builtin special forms really needed are quote, cond and lambda, that’s pretty much it. The only data structure is a list, so functions are just lists, function calls are lists etc.