Let's do one for everything, everyone, and all time. We'll call it E. For Everything/Everyone. And it's two letters ahead of C. Because it's for everyone, it h

Let's do one for everything, everyone, and all time. We'll call it E. For Everything/Everyone. And it's two letters ahead of C. Because it's for everyone, it has to be idiot proof. It'll be strongly typed. It'll use curly brackets, not indentations. It'll give a build error when you do bad practice stuff like have functions that do too many things or name classes on anything that isn't a noun. It's 2021. It'll have AI that checks for bad practices, trained on Uncle Rob's Code Clean. One of the distinguishing features will be plugins. You don't like the rules that E came in? Make your own! Instead of writing binary searches, or setting up network functions and unit tests, everything will just be prebuilt. We have eQuery that simplifies everything. Better yet, we can decentralise that so that everyone can share E code. You can do everything from padding to blockchain with a single import. epm will manage packages and dependencies for you! What if you think E is too restrictive? Maybe you work best with weak typing. Or you think the dates should be yyyy-dd-mm format instead? Or that the prebuilt grey_500 should be gray_550. Then there's TypeFreE, an unopinionated version. Apple doesn't support it? That's fine, just use E Native, which ports everything perfectly on all platforms. Do you worry E is too powerful and may used for evil? That's okay, the whole thing is being maintained by the OpenE Foundation, whose goal is to make sure that E is usable by everyone but restricts access to those who they deem not evil.