It can be used for interactive blog posts and embedded animations etc as well.
It also has a built in animation editor / timeline.
There's 2800+ people in the discord.
And the community made a backup of the site https://archive.canvascommons.io/
Update: sounds like the author had some life changes and had to stop his YouTube channel which was the primary motivator for the library- but there are forks popping up (https://github.com/canvas-commons/canvas-commons).
---
This notion that an open source library is "dead" and shouldn't be used because it's not being actively updated is a bit odd. You can fork and fix issues you have. It's got years of many people's work put into it. It's a great library and widely used on YouTube and elsewhere.
Furthermore, the old docs for Motion Canvas can be found here: https://archive.canvascommons.io/
But- probably reasonably simple, if you mean the "writing" style of manim. That's just animating an SVG stroke.
And then colors and typography
The entire Manim CE Logo example, the `x - x_1` text from the Brace Annotation example, all text from the Sin Cos Plot example, and the entire Heat Diagram example all flicker roughly once per second.
The text looks rather fuzzy, especially the large M from the Manim CE Logo example.
The Three D Light Source example also doesn't appear to have any functioning directional lighting.
- https://github.com/maloyan/manim-web/issues/44 - https://github.com/maloyan/manim-web/issues/45 - https://github.com/maloyan/manim-web/issues/46
The flickering in particular was fixed only on the logo example, but now exists on the Three D Light Source Position example as well.
For issues, may I recommend a more "human-in-the-loop" approach?
(Being AI accelerated doesn't make this project low value. But it does mean _you_ didn't do the port so much as prompt it)
Perhaps that means it's not a question worth asking?
1. Maintenance: Projects that (seem to) have the same quality and complexity but were built over months or years by hand versus built with an AI tool in a weekend will probably experience different amounts of maintenance in the future. This is, of course, not a black-and-white rule. But simply knowing that people think a project is worth spending months or years on gives me an indication that they probably want to keep it alive in the future.
2. Testing: Projects developed by hand probably underwent a lot more hidden manual testing—maybe on different hardware, maybe by more than one person. Since my personal projects have gotten significantly more complex with the availability of AI coding assistance, I spend much more time writing prompts and thinking about integration testing. But this is not the case for all projects.
Tried the live demo and the 3D orbit scene is surprisingly smooth. Curious about a couple things:
- How are you handling the animation interpolation? Manim's rate functions (smooth, there_and_back, etc.) have some quirks that are easy to get subtly wrong. Did you reimplement those from scratch or find a way to match the Python easing curves exactly? - For the py2ts converter — how far does it get on real-world scripts? I have a few older Manim CE scripts with custom VMobjects and I'm wondering if it handles subclassing or if it's more of a "simple scenes only" thing.
One suggestion: it'd be really useful to have an export-to-GIF or export-to-MP4 option directly in the browser (maybe via MediaRecorder API). A lot of the Manim use case is generating assets for slides/posts, not just live playback.
However, I use Manim for maths, for me having computational libraries (python) is a requirement. Most of the transformations that I do are found by using linear algebra, calculus and sometimes full neural networks. All my geometry is computed, not placed by hand.
I'm wondering if it would not be possible to have a 'canvas' backend for the web in the python version instead.
Btw, Manim is kind of easy to install in its own docker ;)
I'm far more into the web than python and have wanted something I could drop into a web page.