Devlog #1: Infinitas Language

You might ask — why?

To be perfectly honest with you, so do I.

My initial drive for creating a new programming language started with my hate towards Python. I hate its syntax, speed, the lack of a formality in language, occasional inconsistency in floating-point and bignum handling.

I also hate that while it is so easy to use, it can also be a huge vulnerability.

Of course, none of these reasons alone amount to creating my own language since a language I create will never be as secure, fast, or bug-free as python. What I just explained you describes my passion and drivers to this project, not my goals.

Development

The language is currently being developed in C++23 (mainly in g++-14), utilizing CMake for build system.

If you ask why I am not using Rust. The answer is very easy.

I don’t know it. I do not want to learn it (yet).

Although I think it would be valuable to address why I used C++ instead of C and the primary reason is to reduce the amount of potential memory vulnerabilities.

What features is it going to have?

Right now I have several features planned.

Cybersecurity Features:

  • Native sandboxing of code snippets and binaries in Linux (and hopefully Windows)
  • Single-line raw socket communication (and web communication) with blocking or non-blocking IO.
  • AI integration for log analysis.
  • Easy integration with common ethical cybersecurity tools.

Language Features:

  • FFI support.
  • OOP and Procedural availability.
  • A C-like syntax with operator overloading.
  • Strong typing with a universal value container (var).
  • A standard library wrapper around native language functions.
  • Read-Print-Eval-Loop
  • Single line webserver hosting for ethical cybersecurity and easy file sharing purposes.

Design Philosophy

I have some strict rules as to what I want out of my language: 1. Operator overloading, separation of primitive functions and user-facing libraries (Infinitas Standard). 2. Fully ready, easy-to-use REPL environment. 3. Fast runtime IR execution (tokenization, parsing, compilation speed comes second). 4. Stability and behavior guarantee — hence I am preparing a formal specification, and unit tests will soon be added. 5. Stable bignum computation. 6. Above all the codebase must be easily understandable.

Where is the project now?

Project Status: The project is NOT a minimum viable product right now. The project, as it is currently, a very buggy piece of software with very limited functionality.

What’s next? I will spend the next couple of weeks to increase the quality of the source code and ensure that it fully complies with the current version of the specification before adding new features.

The entire project will always be open source and you can access it here:

https://github.com/0x221E/Infinitas

I am also writing a specification for it, which can be accessed here:

https://infinitas-spec.atlassian.net/wiki

If by any chance you are reading this…

Please criticize or contribute to the code. I am not a professional software developer, and I really appreciate any input you may have.

Update #1: 2025–11–7

I like python now.