I'm working on an open source tool called noodles.gl that uses this library and it's been great. The devs have been good about keeping a cadence of solid changes and keeping the community updated, and overall I'm happy to have bet on this library years ago.
I love the flexibility and the fact that there's a variety of examples for basically anything I want to accomplish with it. Great work to the team.
Such a sweet story! My friend actually went to the author's Borg party a few weeks ago and I'm second-guessing my choices that night after reading this. Funny to see it on Hacker News!
If you guys like reading about this kind of thing I recommend Cocktail Codex from the people behind Death & Co (referenced in the article). It's a great way to think about cocktails as a remixable grammar and the purpose behind all the mixing, muddling, and stirring.
How about a visual programming language? Plenty of 3D and CAD software uses a VPL for procedural design, which helps a ton to bring out the benefits of both
Grasshopper for Rhino is a big one, or VisualCAD/CAM. Blender, Houdini, or Unreal Blueprints are others. It gives you the exploration benefits of a UI plus the procedural benefits of code. Inputs tend to be auto-bound which makes exploration much, much faster.
I think this is referring to the fact that React uses synthetic event listeners - it's cheaper to bind an event listener once at the root and do your own element matching than it is to continuously bind and unbind listeners.
How does this compare to something like the the Media Capture API? Looks like this uses `canvas.toDataURL()` which can be slow to serialize compared to `toBlob` or `canvas.captureStream(0).getVideoTracks()`
Hi! Insaw this API when I was starting to work on snapDOM but I thought it was not ok for my needs so I discarded it. Regarding other API it would be great if View Transitions API could exposed the old view in a future
Looks cool, somebody should make a package that puts a nice API around it. However seems that those APIs are only in Chrome now, not Firefox or Safari.
They write these emails knowing that they'll be public record at some point. The audience is as much internal as it is for the history books. The details get hashed out offline, while the record gets preserved as an email
For anything more advanced than a simple easing function or some basic keyframes on one or two channels you'll quickly run into the limitations of this approach.
I've been using Theatre.js the last few years and really loving it. It's a library divided into two parts; one is a studio UI with a timeline for editing keyframes and bezier curves, and the other is a runtime for taking those keyframes and interpolating values in relation to a timeline. Try it for anything that requires coordinated animations.
I love the flexibility and the fact that there's a variety of examples for basically anything I want to accomplish with it. Great work to the team.
https://noodles.gl