What were your thoughts, your process... what was your methodology in creating this repository? #980
maitrungdong
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello @juliangarnier,
I was truly drawn to this repository of yours. Maybe it's because your website looks so smooth and beautiful — but more importantly, I feel like this might actually be the solution to a problem I've been trying to solve for a long time.
Let me restate the problem: "How can we play smooth animations on the web — in the browser?"
However, I have to admit that I don’t want to be swayed by fancy words or marketing fluff that clouds my judgment — especially when it comes to stability and performance, which every library/repo tends to praise itself for. (I’ve read many repositories that try to tackle this problem, but I wasn't quite satisfied with how they approached it.)
But this one feels different. (Even though I haven’t read through the full codebase yet.) Just the fact that you named it "javascript animation engine" gives me the impression that you’re trying to build an actual engine to solve the problem in a holistic way — not just patch things together in a fragmented manner. Of course, this is just my impression (since I haven’t explored the full source code yet).
That’s why I genuinely want to understand the methodology behind how you created this repository. You may have your own way of thinking, but here are some example questions that reflect what I’m curious about:
"What is the fundamental nature of playing animations on the web?"
"A website consists of the DOM, CSS, JS, etc., but none of them were originally designed to solve the problem of animation — they were built to render static pages in the early generations of the web. So, what role does each of them play in animation? Where exactly is the animation being played?"
"FPS (frames per second) wasn’t even a concept in the early web. So, when we say we aim for 60fps or 120fps — or talk about web app FPS like in games — what are we actually solving technically?"
...
These are just a few of the many questions that constantly occupy my mind. I've been researching this topic by myself for a while now, and I've never actually asked experts in the field for help — until I found your repository.
It reignited my curiosity and inspired me to reach out to you — as someone who clearly has a lot of experience in this domain — to hopefully get a deeper understanding of your thought process and insights.
I don’t know if I’ll be lucky enough to get a reply from you, but if I do and it helps me gain clarity, I promise I’ll support you — whether through a donation, purchasing a course, or anything else within my ability.
Thank you so much.
Beta Was this translation helpful? Give feedback.
All reactions