No, of course not, it'll never be complete. There's so much we want to do! Add logic programming, for example. Right now the biggest thing going on isn't so visible in Snap! itself, but rather in extensions such as Turtlestitch: We're developing an extension mechanism that will allow such programs to stay up to date with Snap! itself.
Our team:
Paid by SAP to work on Snap! (including curriculum, videos, workshops, talks at conferences, etc., so not full-time developers): Jens, Jadga, Bernat.
Paid by other people for full-time non-Snap! work, but squeezing in contributions when they can: Michael, Joan.
Retired, would do more if more energy: me.
That's it, six of us. The following is an oversimplification, but to a first approximation, our main tasks are these:
Jens: Snap! itself.
Jadga: curriculum, topic of the month, Snap!Con
Bernat: Web site, interfacing with Arduino, Pi, etc.
Michael: Cloud, security, services for teachers
Joan: design review
me: documentation, libraries, herding you lot ;~)
But everyone does a little of everything, the above notwithstanding.
So, the main point is, no, we're not exactly drowning in developers. Gotta say, this is partly because that's how Jens prefers it; he views Snap! itself as his baby, not as a huge distributed effort. We've been more open to collaboration on other stuff, such as libraries and the web site.
I totally agree about the unresolved bug reports. Some of them have been superseded by big rewrites that removed the buggy code as a side effect, but a lot remain current. We do fix things slowly but steadily.
Please be careful to distinguish actual bugs from disagreements with elements of the design. Nobody has the time or the inclination to make skins/themes for the editor or the website. Sorry.
I'm not sure exactly what you mean by a stable version. I think we've been pretty good about things like supporting old projects and not just randomly crashing. With 9.0 there were a few problems that showed up as soon as people other than us used it, which is why there have been a dozen 9.0.n releases up to the current 9.1.0.
We have a mechanism for creating uniform and readable help screens. We are slowly migrating to vector costumes (although also adding Meghan Taylor's gorgeous watercolor costumes, uniquely ours). We know about the slow loading of the choosers for costumes etc., and we know how to fix it too, but someone has to get around to it. I agree that that should maybe be higher priority than it's been. But, honestly, you want different costumes? Go for it! You can load pretty much any picture file into Snap!.
Snapinator was written by a high school kid and then rewritten by another high school kid. I think we'd be totally open to someone else taking that on. Snapp! was also an external product, although done by an adult; it would be great if someone wanted to update it.
Snap! 's core purpose is to help teenagers learn computer science, both in school and independently. When we're not sure if we're doing the right thing, that's where we focus our attention. That focus has two parts to it. The more straightforward one is that we want to be a super powerful programming language. First class procedures, lists, and sprites are the central ideas in this area. We've added first class continuations, costumes, sounds, and databases/spreadsheets as two-dimensional lists. Hyperblocks give us very efficient multi-dimensional array support. The other part of our teaching mission is the one we inherit from Scratch: using visual program elements to make the big ideas accessible to beginners. My paradigmatic example is the idea of program as data. Someone who's never seen that idea before, but who knows what Scratch blocks look like and knows what Scratch lists look like can see a picture like
and just immediately get it, in a way that no amount of explanation could match.
But that doesn't mean Snap! isn't also for other things. Yes, games. Yes, math. Yes, kids.
Sigh. I'm pretty sure I've answered this 20 or 30 times. If this were the 20th century we could be looser about this, but the entire world is paranoid about protecting children from low-probability risks and we don't have the resources to fight that battle. I don't like it any better than you do. It would be much better, in my personal opinion, if they worried instead about high-probability risks such as child malnutrition, child malaria, or children's houses being bombed. BUT, discords and bots have nothing to do with the Snap! programming language! The purpose of Snap! certainly isn't to provide a social network for programmers. You want to make a Discord or a subreddit or something about Snap!, just don't tell us, make sure it says in big letters that it's not official, and don't advertise it here. And for the love of god don't arrange f2f meetings with strangers without an adult present.
Censor yourself to bypass the filter is so funny and smart (not talking about you, don't worry)