If it doesn't just go away in another couple of weeks, I think I'm going to sacrifice an evening or two to writing out the ideas and hope that satisfies my subconscious that something came of it and it's OK to drop the idea now. I mean, in some sense, the best case is to publish it, get it on to Hacker News, let it go infect someone who does have the time to deal with it, and then use their language when they're done.
I'm hoping perhaps even typing this much may do the trick...
There's a lot of winds blowing against a new language, but this is one of the rare winds blowing for it; it can literally be easier to write a new language from scratch and boot up a new culture than it can be to change an existing culture. For example, it wouldn't matter if C++ imported every Rust feature, even for the sake of argument to the point where this new (terrible monstrosity of a) compiler could literally compile all current Rust code. The result still wouldn't be "Rust", or able to "kill" Rust, because the sheer inertia of C++ culture (or, for a language this big, "cultures") would simply never produce the sort of code that you see in real Rust.
I think the goals are great but addressing them at the architecture level is better, especially with tools to really take advantage of that modularity. Something like this:
https://github.com/LiveAsynchronousVisualizedArchitecture/la...