Hi! I'm the lead author of Spritely here. Totally understand that sentiment, and you're not wrong that it's hugely ambitious.

So, Spritely's approach to vaporware avoidance is to break things into subprojects and show how we're making progress with demos. If some of the subprojects fail, but the others still exist and are useful independently, that's a big win.

Spritely Goblins is already quite usable, and does quite some interesting things: https://docs.racket-lang.org/goblins/index.html

Even if that's all that succeeds from Spritely (and I don't think it will), I think that's a useful contribution.

But seeing is believing, and skepticism is well warranted. All I can say is, I hope that in two years we can come back to this post and re-evaluate it and see how far Spritely is along. I hope we can prove ourselves. I'm working very hard to do so.