There’s nothing wrong with Sclang staying Sclang (and there are many benefits!). We don’t actually need to change at all: people are happily writing music every day, and as CPUs get faster their code gets slightly zippier. We have a native language that works for many people (it’s extremely rare that I myself write Sclang, but who cares?). There’s a great value to local communities.
It’s not so much saying that sclang should die, but more accepting the reality that the language and the IDE are effectively stagnant at this point. Legacy products can continue for years, they just don’t get any improvements. If you like sclang as it is, keep using it. If you’re okay with the IDE, keep using it (and hope that QT doesn’t go away). But for people who want something, or something better, maybe it’s better to invest energies elsewhere.
In an ideal world someone would take SuperCollider, build consensus as to what the language needs to look like going forward, and then would have the time and skills to make that happen relatively quickly. In the real world, none of these seem remotely plausible
People, imo, need to “vote with their feet.” I added a Haskell client to the world, for anybody who wanted to use. Most people preferred the default (sclang), which is great. The more the merrier. If there’s true fragmentation (like a 50-50 or even a 70-30 situation), maybe it’s time to talk about a top-down solution. But at the moment, people are choosing Sclang and Tidal and Sonic Pi as SC clients.
Well that’s partly due to marketing/promotion. Alex Mclean is really good at promotion, and so this has helped Tidal enormously (there is a lot to learn from Alex. He’s a force of nature). Sonic Pi also had someone running it who was good at promotion, and he’s created a really engaging interface that sucks people in. Obviously both of them are good products. But seriously, a coding language in an obscure/difficult language, that allows you to do gabber/carnatic rhythms. Who would have bet on that being successful…
I only came across vivid (I assume that’s your client) because I was already using Haskell. There’s no reference to it on the SuperCollider site, and it’s official presence is in the (intimidating to non-haskell users) Hackage documentation. Given that Haskell is a relatively unpopular language, and SuperCollider is a relatively unpopular music environment, I don’t think lack of interest in what you did is that surprising. Interest was always going to be limited to the subset of people interested in SuperCollider and Haskell.
On the other hand if another language was picked as an official ‘successor’, and was promoted (preferably with a simple one click installation for newbies, and a platform appropriate install for experts with that language), it would do fine. Most people when confronted with a choice between a language that they’ve never heard of and JavaScript/Python - well they’re not going to choose the obscure one.