What If Python-Like Syntax Could Build Native Rust Applications?
There is an interesting space between the simplicity of Python and the power of systems programming.
Python is known for being approachable and productive.
Rust, on the other hand, gives developers strong typing, native performance, memory safety, and access to a powerful ecosystem.
But what if you could explore some of that middle ground without giving up a familiar, readable syntax?
That's what caught my attention about Incan.
What is Incan?
Incan is a statically typed programming language designed around a Python-shaped source experience while producing native, Rust-backed artifacts.
The idea is interesting because it doesn't simply try to be "another Python" or "another Rust."
Instead, it explores a different balance between:
Readable application code
Static typing
Native binaries
Rust-backed execution
Systems-level interoperability
Access to the Rust ecosystem
Why is this interesting?
For Python developers, native deployment and stronger correctness can become important as applications grow.
For Rust developers, application-level code can sometimes involve more ceremony than necessary.
And for developers working with native libraries, interoperability can be an important part of the equation.
Incan is exploring whether a different language design can make these areas feel more approachable while still targeting native systems.
Incan 0.5
The recent 0.5 release is particularly interesting because the project has moved beyond just experimenting with syntax.
The release introduces capabilities around building applications, libraries, and larger multi-package projects.
Some of the notable areas include:
Multi-package workspaces
Larger projects can be organized into multiple packages with shared configuration and dependency management.
Typed C ABI interoperability
Incan 0.5 also introduces bounded C ABI interoperability, opening the door to integrating with native C libraries.
Stronger standard-library capabilities
The project has continued expanding its standard library for practical application development, including areas such as file handling, streaming, hashing, environment access, and other application-level functionality.
Better tooling
The release also brings improvements around diagnostics, declarations, code intelligence, and compiler/package-boundary handling.
The project is still in beta, so there is obviously plenty of room for experimentation and improvement.
And that's actually one of the things that makes it interesting to me.
Who might find Incan interesting?
I'd be particularly interested in hearing from:
Rust developers interested in application development
Python developers interested in native deployment
Developers working with C/native libraries
Programming-language enthusiasts
Compiler and tooling developers
Open-source contributors
I'm curious about what developers think of this approach.
Would you try a language that combines a Python-shaped source experience with native Rust-backed artifacts?
What would you need to see before seriously considering it for a project?
You can explore the project here:
GitHub: https://github.com/encero-systems/incan
And if you're interested in the 0.5 release, the release notes are available here:
Incan 0.5: https://incan.io/dev/release_notes/0_5/
I'd genuinely love to hear what developers think about the idea especially from people who work with Rust, Python, C interoperability, or programming-language tooling.
Top comments (0)