openrndr VS deno

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.

NodeJS is the dominant Javascript server runtime environment for Javascript and Typescript (sort of) projects. But over the years, we have seen several attempts to build alternative runtime environments such as Deno and Bun, today’s subject, among others.

https://github.com/denoland/deno/issues is the ideal place -- we try to triage all incoming issues, the more specific the repro the easier it is to address but we will take a look at everything that comes in.

Install Node.js (or Bun, or Deno, or whatever JS runtime you prefer) if it's not there

QUIC is very exciting, after seeing what it can do for performance in Cloudflare network and Cloudflare workers, I can't wait to finally see it in Deno[0] 1.41.

[0] https://github.com/denoland/deno/pull/21942#issuecomment-192...

So as an end user it's kind of like https://deno.com/ where you buy into a runtime + comes prepacked with DBs (k/v stores), scheduling, and deploy stuff?

> by storing Unison code in a database, keyed by the hash of that code, we gain a perfect incremental compilation cache which is shared among all developers of a project. This is an absolutely WILD feature, but it's fantastic and hard to go back once you've experienced it. I am basically never waiting around for my code to compile - once code has been parsed and typechecked once, by anyone, it's not touched again until it's changed.

Interesting. Whats it like upgrading and managing dependencies in that code? I'd assume it gets more complex when it's not just the Union system but 3rd party plugins (stuff interacting with the OS or other libs).

~90MB+ at this stage and do now allow compression without erroring out. Deploying ala Golang is not feasible at that level but could well be down the line if this dev branch is picked up again!

The exe output grew from from ~50MB to plus ~90MB from 2021 to 2024: https://github.com/denoland/deno/discussions/9811 which mean Deno is worse than Node.js's pkg solution by a decent margin.

Behind the scenes is a simple Sveltekit-powered server function to fetch a Spotify client token then find a user's recommendation playlist and its track information. A Deno edge function to performs this data fetch and renders server-side Svelte.

If your application is written in JavaScript, integrating it with JavaScript extensions is a no-brainer. However, Secutils.dev is entirely written in Rust. How would I even begin? Fortunately, I recently came across an excellent blog post series explaining how to implement your JavaScript runtime in a Rust application with Deno: