WestLangley

>`sub` means `under` to me. Correct. It does. I am inclined to agree that `Vector3.sub()` is a poorly-named method. Whether it is worth changing at this point is a judgement...

We are talking about the `Vector3` class here. You can change `.multiply()` to `.mul()` and `.divide()` to `.div()` -- if you really think the conventional terms are too verbose. Or...

>sub() is a valid counterpart to add(). In English, no. It's add, subtract, multiply, and divide.

@mrdoob tldr; For consistent nomenclature in the `Vector3` class, either use `add()`, `subtract()`, `multiply()`, `divide()`, or short forms: `add()`, `sub()`, `mul()`, `div()`, but do not mix them.

Is adding skinning/morph support to `PointsMaterial` what you are looking for?

@takahirox Yes, we would have to fix that somehow, if we were to add skinning/morph support to `PointsMaterial`.

>But maybe having skinning/morph support in PointsMaterial would satisfy the users who just wanna render SkinnedMesh with gl.POINTS. That would probably also require a `SkinnedPoints` class -- in addition to...

>The new node material provides a beautiful solution for this use case Were you able to get that to work with `WebGLRenderer`?

>However, @WestLangley had objections against the PMREM solution (see https://github.com/mrdoob/three.js/issues/20115#issuecomment-675644813). I would only rewrite the PR if he agrees on PMREM, too. I appreciate that, @Mugen87, but I don't want...

>@WestLangley do you have a preference between these, or other ideas? Color spaces are well-defined, so I do not see the benefit of listing the transfer function, primaries, and white...