What was and what was not Fabric Engine?

cg news

A couple of weeks ago Fabric Software abruptly ended the development of Fabric Engine without any following announcements. In this two-post series, I’ll try to go over what Fabric Engine was, the different positionings it assumed through the years, and what voids does it leave in the CG community. Bear in mind these are my own personal opinions.

Update, check the second post in this series: Fabric Engine and a Void in 3DCC Machine Learning.

In the beginning, there was KL

From the start, Fabric Engine was a “high-performance computation platform” (https://goo.gl/muzRzV) it was not supposed to be a plug-in for Maya or other DCCs (https://goo.gl/SxqzxG). Anything one would want to compute in Fabric needed to be coded in its own special language called KL. KL was an object-oriented scripting language with JavaScript syntax. Its big plus over something like Python, for example, was its just in time compilation and parallel computing capabilities. So, it was fast.


Fabric Engine’s main components

However, why was it any good for CG folks?