Precisely - every reverb is impulse response, lots of other effects are effectively some sort of convolution with neural networks that we otherwise call AI. Arpegiattors are AI and the random jumps between patterns in Ableton are a Markov Chain.

What does Bandcamp really mean? Perhaps sampling others voices and music is barred, not these mini-AIs that are everywhere ?

Please stop being intentionally obtuse. Convolution, arpeggiators, impulse responses are not at all comparable to output from generative AI / LLMs.

Author fails to recognize the fact that CLI agents make all kind of hoisting easier and fun. Like publishing to CloudFlare Pages which costs close to nothing and now takes seconds, while previously could taker days.

System Concierge, not sysadmin.

Doesn’t seem to work on mobile for me on ios18 and iphone12

Claude Code does a very decent UI, somehow the text mode is much more attractive. As if there is once in a lifetime opportunity to make the console great again.

Really, inst there anything which comes Slug-level of capabilities and is not super expensive?

Vello [0] might suit you although it's not production grade yet.

[0] https://github.com/linebender/vello

Just use blend2d - it is CPU only but it is plenty fast enough. Cache the rasterization to a texture if needed. Alternatively, see blaze by the same author as this article: https://gasiulis.name/parallel-rasterization-on-cpu/

Check this out: https://thorvg-perf-test.vercel.app/ https://www.youtube.com/watch?v=jdnnzmtHy9k

ThorVG might be worth a look - open source (MIT), ~150KB core, GPU backends (WebGPU, OpenGL).

We are using it as official dotLottie runtimes, now a Linux Foundation project. Handles SVG, Lottie, fonts, effects.

https://github.com/thorvg/thorvg/

In terms of performance, it's quite far from something like Blend2D or Vello though.

Blend2D is a CPU-only rendering engine, so I don't think it's a fair comparison to ThorVG. If we're talking about CPU rendering, ThorVG is faster than Skia. (no idea about Blend2d) But at high resolutions, CPU rendering has serious limitations anyway. Blend2D is still more of an experimental project that JIT kills the compatiblity and Vello is not yet production-ready and webgpu only. No point of arguing fast today if it's not usable in real-world scenarios.

How JIT kills compatibility if it's only enabled on x86 and aaarch64? You can compile Blend2D without it and it would just work.

So no, it doesn't kill any compatibility - it only shows a different approach.

BTW GPU-only renderers suck, and many renderers that have GPU and CPU engines suck when GPU is not available or have bugs. Strong CPU rendering performance is just necessary for any kind of library if you want true compatibility across various platforms.

I have seen many many times broken rendering on GPU without any ability to switch to CPU. And the biggest problem is that more exotic HW you run it on, less chance that somebody would be able to fix it (talking about GPUs).

Good ! Finally someone does it, sadly I didn’t have the time been planning for 1 year now.

Was this posted automatically or why it reads Vienam? Without the T! And the title also reads so?

I posted it with the original article title. I'm not sure who changed it, but yeah, there is a typo which also exists in the linked article.

Indeed it first had no T, and s.o. changed it. Also raises questions reg the original title.

everyone understood overnight what vibe-coding was, but only dared to go through the looking mirror and try to grok what the mirror is made of.