Thanks Daniel for weighing in! I agree that there have been features added on the side of teachers running Desmos/Amplify Activities but my comment was intended primarily to be about Computation Layer (i.e. the programming/glue that allows activity authors to make better activities) and to some extent about the ergonomics of writing activities.
The ability to copy and paste individual components has been excellent and at least reduces the amount of typing of CL code, although it also means that any improvement to be made in one section of code is more likely to be scattered across multiple screens and multiple activities (as opposed to a model where code is stored separately in libraries and then an improvement in one place would affect all the components calling the given function/s).
I had forgotten that those list functions were added to Computation Layer (List Functions in CL) although I would really like to see these, and patterns, properly documented.
Maybe the title of abandonware is inaccurate in hindsight, and in fact it’s mainly the fact that the documentation is in need of refreshing. However, I had also assumed the underlying language would evolve to be more like a fully fledged declarative language, and it appears that isn’t the direction.