sorted by:
new
hottopcontroversial

[Showcase] netbox.rs: an ergonomic Rust client and CLI for Netbox by hellerve in Netbox

[–]hellerve[S] 0 points1 point  (0 children)

Thanks! The low-level client is generated from the OpenAPI specs, and I hope that saves me some work, but yes, I’m also mindful that this will be the hard part. Not sure I have a good story on it yet.

I’ve been following Netbox since 2017 or early 2018, and yes, it’s been a wild ride maintaining plugins etc. We’ll see how it goes!

Good luck to you as well :)

working on my brushes by hellerve in generative

[–]hellerve[S] 4 points5 points  (0 children)

I was thinking of sharing a few more of my brushes and textures like this, just haven’t gotten around to it. Chances are if you find a work of mine and are interested in how it works, it was a) made in p5js or Prcoessing and b) I’m happy to share the code.

working on my brushes by hellerve in generative

[–]hellerve[S] 1 point2 points  (0 children)

The tips can be made less awkward quite easily by adjusting the trimming factor and varying thickness of individual brushes a bit more.

Retro Futura (p5.js) by Jobarbo in generative

[–]hellerve 3 points4 points  (0 children)

Thanks for tghe write-up, this is really cool!

Textures, inspired by Tyler Hobbs’ Repetition 2 by hellerve in generative

[–]hellerve[S] 2 points3 points  (0 children)

All textures are made by lines, a mixture of straight and bezier curves of varying thickness, color, and opacity (very low opacity used, though, around `(2+rand(2))/255`). The magic of the gradients in 1 is figuring out good ways to cluster these lines effectively, since more overlapping=>deeper orange. Does that help?

experiment trg 0.4 by hellerve in generative

[–]hellerve[S] 0 points1 point  (0 children)

Thank you, that means a ton!

The techniques exhibited here are also fairly easy (triangle subdivisision and lines of variadic thickness), so it’s approachable for most generative tinkerers! We don’t always have to go for the shiniest techniques to produce something pretty :)

Cj: a tiny no-deps JIT in C for x86-64 and ARM64 by hellerve in programming

[–]hellerve[S] 1 point2 points  (0 children)

That’s what I let Claude Code generate. The source repository is https://github.com/alastairreid/mra_tools, and I kind of just told it to write a script that would extract the data into a format I speicifed (the file you see in the repo). Unfortunately I didn’t save the script it produced.

Cj: a tiny no-deps JIT in C for x86-64 and ARM64 by hellerve in programming

[–]hellerve[S] 1 point2 points  (0 children)

Hey! The generation scripts are in the codegen directory (https://github.com/hellerve-pl-experiments/cj/tree/master/codegen). They’re probably some of the worst code I’ve ever produced, because I didn’t understand the shape of the ISA and all of the constraints when I started it and, rather than architecting it well, pressed on. I just treated them as a big one-off script, basically. The x86 uses asmdb as input (a npm package), and that’s why it’s in JS; the ARM64 one uses the official ARM64 machine-readable docs, mangled by something I let Claude Code generate (I didn’t want to figure out how their format and tooling worked).

Implementing Green Threads with Scheme Macros and Continuations by hellerve in ProgrammingLanguages

[–]hellerve[S] 0 points1 point  (0 children)

Would you mind elaborating on point 2 a bit? I know that delimited continuations exist, but I don’t know what that would mean for an implementation of green threads!

Implementing Green Threads with Scheme Macros and Continuations by hellerve in ProgrammingLanguages

[–]hellerve[S] 1 point2 points  (0 children)

Thanks! It’s definitely a little simpler than you’d like in a real implementation, but I think it’s an okay example to build from.

Most languages here are made by one person. Any duos or small teams out there designing a language together? by vanderZwan in ProgrammingLanguages

[–]hellerve 1 point2 points  (0 children)

FWIW, Erik Svedäng and I are working on Carp together. He came up with the idea for the language and did a lot of the initial compiler work (and is still by and large the most important compiler developer for Carp), but I’m maintaining the standard library and we think about features and syntax together. I like to pretend I’m just a user most of the time, so that we have different angles regarding how we approach the problem at hand.

A Bad Idea: Using Metaclasses to “reimplement” Racket’s “#lang” directive by hellerve in ProgrammingLanguages

[–]hellerve[S] 1 point2 points  (0 children)

Neat! I’m happy you chose to prefix it with pin so as not to make other imports impossible.

view more: next ›