openrndr VS website

I've been having fun making generative art for a few years and recently got the itch to write my own JS library for sketching SVGs.

This library is heavily inspired by OPENRNDR [1], which to date has been my framework of choice.

My motivation to write a JS library for SVGs came from a desire to bring the programming style I love from OPENRNDR into a language I use every day. I was also motivated to generate simple SVGs that I understood deeply because I'd like to start using a plotter soon to bring these sketches into the physical world.

The library is pretty bare-bones, but I did my best to document it thoroughly enough that a beginner could install it and draw their first sketch in as little time as possible. All the documentation, including an FAQ, is hosted in the project Wiki [2]. And yes, I do recommend p5.js for most users/beginners, but I still believe this library fills a niche.

Happy to answer any questions, or field any criticisms/notes.

[1] https://openrndr.org/

I am primarily using the openrndr framework to do all of this.

Last year I wrote Kosmik, a Twitter bot for pixelized retro-style space images in Scala, but I was dissatisfied for several reasons, performance being one, so I migrated the code to Kotlin using openrndr as graphics API recently, and moved the bot to Mastodon. What do you think?

Is there a framework, library or package along the lines of Processing or OPENRNDR for Common-Lisp or Clojure etc.?

I’d also be interested in peoples replies. I know there is a creative coding framework built on it (haven’t used it though) https://openrndr.org/ .

Kotlin is very similar to Swift. OpenRNDR is a coding framework written it it. Kotlin has many of the features you speak of. Kotlin supports many of the features you ask about (or at least something similar to it).

Also have you checked out https://openrndr.org/

After trying to use Processing with Kotlin I discovered OPENRNDR. This is a new-ish creative coding framework created in Kotlin and it runs on the JVM. I'd say the performance is somewhere around what's typical of Processing (so pretty good), it also supports shader programming if you want to squeeze more out of it.

This happened few years ago I don't remember the specifics, but I find funny to see the exact confusion still around whats supposed to be a basic functionality here with the k8 devs themselves acknowledging lack of correct docs but doing little.

Great to know! Since the kubernetes/website repo currently lacks the tr localisation, I'm pretty sure starting it there would be much appreciated by the relevant community. This guide and the #sig-docs-localizations channel in Kubernetes Slack are the best starting points for those who might be interested in it.

From the doc:

Better is probably subjective, but you have options. You can run the doc website locally (https://github.com/kubernetes/website) or search the API definitions directly (https://github.com/kubernetes/api). Good ol `git grep` I suppose.

No, I don't think so. Killercoda is one of the main options currently being considered for moving from Katacoda. You can find this discussion here.

Kubernetes*

I'm unable to find any references other than this link that confirms that the failure has to be consecutive. https://github.com/kubernetes/website/issues/37414

Discover the full power of this feature in the docs.