Pinned post
Since so few people see my X posts these days, might as well just record this here: I am designing a new _type_ of programming language. It's not ready to share yet, not even close, despite working on it 4 - 6 hours a day since November 2025. However, when I'm done the language will provide:
- Near-perfect static analysis. Write any rule you want and have it enforced deterministically. Automatically refactor anything and be totally confident the refactoring was safe.
- Fast automated verification as part of the language itself. Not necessarily full formal verification automatically during compilation, but something similar. Specifying the program sufficiently for this verification will be a mandatory part of the language. Separate proofs could be written to fill in any verification gaps. Plus, the language will automatically generate property tests to prove the runtime properties of the system.
- Only one way to write any correct program. This is impossible in the limit, but the language will get closer to this than any other language has ever come, as far as I know, and the static analysis properties will allow developers to specify the other rules they would need in their environments to make it true for the software they are building.
- Theoretically perfect optimization. Once again, extremely difficult, but the language will provide maximal knowledge of the system to the compiler, enabling the compiler to some day reach a level of optimization beyond any other language in existence today. Reaching that actual maximum could take a decade or more, but the theoretical peak should be there, from what I can see so far.
- Fast compile times with a high degree of parallelism during the build. Probably not as fast as Go, but it should be faster than Rust (though the specifics here remain to be seen). Also very good incremental build behavior to avoid recompiles, although with an option to do full optimizing analysis of the whole program for better performance.
- Automatic concurrency. Get maximum efficient parallelism without ever writing a single concurrency construct. Get verification of safe concurrency at compile time. The "maximum" part is actually easy, with the language's design. The "efficient" part could take quite a bit of work but I believe we could get there (since we will have near-perfect knowledge of the system).
- Way more stuff, including what I think are some of the best supply-chain security principles and large-scale software development support in the world.
Once of the reasons it's not ready to share is that these are some pretty wild claims, and I want to have an actual artifact that shows that it works before I go advertising it very broadly. There is also the chance that I'm wrong or that I will hit some impassable wall at some point, although so far everything has been working out pretty wildly well. And finally, I can't field a zillion questions or write its docs right now while I am deep in its implementation. (All of that will come later, and I have plans for how to make the language accessible to both humans and agents, as well as provide a great tooling ecosystem around it.)
Right now the only real barrier to its development is how much time I have to work on it. I have a day job that I genuinely love, with co-workers who I really appreciate and enjoy working with. But because of that, I only have about 6 hours a day (yes, I am working 14+ hours a day) to work on this, and even with agents it is a project that requires thousands of hours.
If I could find some way to work on this full time, I would be doing it 12+ hours a day. I am confident that this is what the world of agentic software development needs right now. I am confident that I can build it. I just need the time.
- Near-perfect static analysis. Write any rule you want and have it enforced deterministically. Automatically refactor anything and be totally confident the refactoring was safe.
- Fast automated verification as part of the language itself. Not necessarily full formal verification automatically during compilation, but something similar. Specifying the program sufficiently for this verification will be a mandatory part of the language. Separate proofs could be written to fill in any verification gaps. Plus, the language will automatically generate property tests to prove the runtime properties of the system.
- Only one way to write any correct program. This is impossible in the limit, but the language will get closer to this than any other language has ever come, as far as I know, and the static analysis properties will allow developers to specify the other rules they would need in their environments to make it true for the software they are building.
- Theoretically perfect optimization. Once again, extremely difficult, but the language will provide maximal knowledge of the system to the compiler, enabling the compiler to some day reach a level of optimization beyond any other language in existence today. Reaching that actual maximum could take a decade or more, but the theoretical peak should be there, from what I can see so far.
- Fast compile times with a high degree of parallelism during the build. Probably not as fast as Go, but it should be faster than Rust (though the specifics here remain to be seen). Also very good incremental build behavior to avoid recompiles, although with an option to do full optimizing analysis of the whole program for better performance.
- Automatic concurrency. Get maximum efficient parallelism without ever writing a single concurrency construct. Get verification of safe concurrency at compile time. The "maximum" part is actually easy, with the language's design. The "efficient" part could take quite a bit of work but I believe we could get there (since we will have near-perfect knowledge of the system).
- Way more stuff, including what I think are some of the best supply-chain security principles and large-scale software development support in the world.
Once of the reasons it's not ready to share is that these are some pretty wild claims, and I want to have an actual artifact that shows that it works before I go advertising it very broadly. There is also the chance that I'm wrong or that I will hit some impassable wall at some point, although so far everything has been working out pretty wildly well. And finally, I can't field a zillion questions or write its docs right now while I am deep in its implementation. (All of that will come later, and I have plans for how to make the language accessible to both humans and agents, as well as provide a great tooling ecosystem around it.)
Right now the only real barrier to its development is how much time I have to work on it. I have a day job that I genuinely love, with co-workers who I really appreciate and enjoy working with. But because of that, I only have about 6 hours a day (yes, I am working 14+ hours a day) to work on this, and even with agents it is a project that requires thousands of hours.
If I could find some way to work on this full time, I would be doing it 12+ hours a day. I am confident that this is what the world of agentic software development needs right now. I am confident that I can build it. I just need the time.