Thanks for confirming that my suspicions were unfounded. Not knowing any different, it appeared to me from the posts in this lengthy topic that the core openscad was going more or less all python, at a very fast rate. I am happier working with a small set of stable operators, compared to cutting and pasting existing code from different sources. These days, that is seen  as being  'old fashioned'. That is OK, until the chickens come home to roost, so to speak. On 14/05/2025 18:55, Marius Kintel wrote: > On May 14, 2025, at 13:46, Raymond West via Discuss > <discuss@lists.openscad.org> wrote: >> >> How many folk need to be interested for openscad to include >> Javascript, Fortran,or more appropriately APL? >> > JavaScript could be a decent option, as a lot of people familiar with > it. The others are probably for more specially interested folks. > JavaScript has one big advantage over Python in that is offers good > sandboxing support, so it can be enabled by default without any > security caveats (as long as we sandbox things like networking access > properly), but is has similar challenges to Python in terms of pulling > in large 3rd party libraries. > >> The stable release of openscad is dated 2021, is fiddling around with >> python going to further delay a stable release to the general public? >> > Don't worry: The next stable release is completely decoupled from > Python-related developments, and the next official binaries are very > unlikely to include any Python features. Our primary goal going > forward is to reduce acceptance of new features and work primarily on > stabilizing existing features leading up to a new release. > >  -Marius >