FAQ

Honest answers to common questions.

What is RUDRA?

A compiled, statically typed systems language. Its compiler, ruxc, is written in RUDRA itself and turns a source file into a native x86-64 Linux executable.

Which platforms are supported?

The current 1.1.0 release targets Linux x86-64 only, as a tarball and a .deb. The 1.0.0 and 1.0.1 releases were the earlier Rust-based toolchain, which had macOS and Windows installers; those are not the current toolchain. See Downloads.

Are the distributed binaries dependency-free?

Yes. ruxc is a static ELF with no runtime dependencies, and the executables it produces are static ELF files too. They are not dynamically linked.

Does RUDRA support threads, channels and HTTP?

Not as language built-ins. There are no spawn, mutex, channel, http_get or json_get builtins. The standard library contains modules such as thread, net, http and json, but they have documented limits and should not be treated as production networking. TLS cryptography is implemented in RUDRA, but it is not wired into a live authenticated HTTPS client. See Transparency for exact statuses.

Is there a package registry?

No. The 1.1.0 release does not include ruxpkg. A manifest-verifying package tool exists in the source repository but is not yet released, and no public package directory is published on this site.

What is the license?

The RUDRA toolchain is free to use, including commercially, and the programs you build are yours. The authoritative license text is the LICENSE file in the repository and the LICENSE file included in each release.

How do I report a bug or request a feature?

Use the GitHub Issues tracker for bugs and GitHub Discussions for proposals. See Developer Hub and Community.