This past semester, THREE.js dropped support for THREE.Geometry, changing the way to present procedurally created geometries to THREE.js. This broke most of my currently existing interactives, and has me rethinking how I want to present the idea of geometries to my students.
- Is it okay to plan on teaching a course based around such a dynamic (and I guess theoretically untrusted) third-party library?
- I have an old copy of THREE.js. Is it okay to teach a course asking my students to work with this old copy? (a separate question is whether this would be pedagogically a better presentation of the topic, which I asked on computergraphics.stackexchange: https://computergraphics.stackexchange.com/questions/12406/which-provides-better-intuition-three-geometry-or-three-buffergeometry)
- How do you live like this? I jest, but I would really appreciate some insights into teaching in such a dynamic field, where specifics I teach my students might not work in a year's time and general concepts might be out-of-date in five years.