react-motion VS slate

Github repo : https://github.com/chenglou/react-motion

React-Motion is an animation toolkit that makes building and implementing realistic animations much easier. However, React-Motion can be hard to grasp for beginners. But it has good documentation with rich examples to help developers.

React Motion is an animation library for React applications that makes realistic animations easier to build and implement.

Here's a comparison showing how the transition-hook bundle size compares to other React animation libraries: react-spring, framer-motion, react-motion, and react-move:

Framer Motion is a production ready animation library for React. I felt the need to add some "cool" animations to my portfolio so that it looks more alive and interactive. One can argue between choosing React Spring or React Motion but that depends on the use-case and since I've already worked with Framer motion before so I went with this.

Ah I found it. "On the Spectrum of Abstraction" by Cheng Lou (author of React-Motion)

https://github.com/chenglou/react-motion

React Motion

Thanks. Let me write some information concerning our ClojureScript frontend. We wanted to use physics-based animations using springs since only these animations make sense. Sadly the browser decided to only support silly animations which are described in terms of curves and durations. Spring animations are used on both MacOS and iOS and they look much better, since they have the natural feeling. Originally, we were using React Motion for them which would be fine for a small project. But running a lot of animations at the same time is very taxing since every frame of the animation has to go through React and all these layers. Therefore, I spent about 4 months completely rewriting most of our frontend code related to rendering and UI interactions within OrgPage. Unlike React Motion and probably any other spring-based animation library, we do not simulate these springs but instead analytically solve their differential equations. (Luckily I have a strong background in math.) I created the OrgPage https://orgpad.com/s/yRyR-GOU0Pm which summarizes math and my approach. Our animations code consists of about 5k lines of code where maybe 1k is the physics itself and computation of animation maps. The remaining 4k lines are low level controls where particular OrgPage elements are animated using requestAnimationFrame. We always calculate their new positions/sizes/etc. and apply DOM mutations, completely bypassing React, Reagent and Re-frame. There are a lot of clever optimizations to get the current speed. In upcoming months, I plan to investigate WebGL rendering which we could use to render larger parts of the documents, hopefully making everything even faster.

react-motion - A spring that solves your animation problems

Motion/transitions, powered by react-motion

- it creates a layout based on rows and cells, so it support multi-column layout - each cell can contain a different "cell-plugin", - richt-text editor based on https://github.com/ianstormtaylor/slate is built in and comes with its own plugin system. It can do weight, italic, block-types, alignment and lists and can be extended as you want (even with elements storing data and interactive components) - you can create custom cell plugins based on a schema (or custom control ui) and a component that should be rendered - it stores an object tree that represent it, not html. It therefore can contain any react component, which is great if you want to allow your editors to add interactive components or components that you already built as part of the app - i carefully optimized for SSR and bundle size, so no editor ui is rendered nor loaded. editor ui is only loaded on the client if you disable readOnly. (lazy loading) - it mainly tested with nextjs, since i used it for content-heavy pages. - its not yet tested with react-server components, but it should actually work in read-only mode

Finally there's Slate and Lexical which are super powerful in terms of customizability and extensibility. They're great options for when the editing experience plays a major role in the product.

Slate, as per its documentation, is a completely customizable framework for building rich text editors. Therefore, it doesn't offer a feature-rich text editor but instead provides tools to build one. Let's create a component called Slate and see what the Slate editor looks like.

Link to Repo

Word of warning about Slate: I love the API and the design goals, but it appears to suffer from some fundamental issues. We were experiencing issues similar to this one and a team of multiple 10+ year experienced frontend devs couildn't figure out what was going on. I had to completely rip out a feature we had built with Slate and had to reimplement a new version from scratch with Lexical. So far we have no issues other than those inherent to rich text editing.

We're trying to choose between Lexical and Slate at work. Do you have any examples that would be similar to this? https://github.com/ianstormtaylor/slate/blob/main/site/examp...

If you are going to customise a ton of functionalities and/or implement new functionality I suggest using SlateJS. If not, have a look at Sun editor.

You definitely need to give Slate (https://github.com/ianstormtaylor/slate) a try - the best editor framework I've used.

Slate: Looks very promising, but it's for React. (Someone has floated the idea of making it framework-agnostic, but the maintainers haven't committed to that goal yet.)