It's the first release--early bird pricing to raise funds for development.
6 karma · joined November 30, 2024
It's the first release--early bird pricing to raise funds for development.
I was curious to see if I could do something like this for fun. It currently works with 111 languages from the 40/50s-today.
I built something I wish I had years ago.
USL (Universal Scripting Language) is a symbolic syntax system that lets you write logic once, and output that logic into 111+ real programming languages — Python, Rust, C++, JS, Java, Go, etc.
Upload a .usl file into the hosted app → choose any language(s) → download a .zip of the real code.
It supports:
Symbolic logic for print, assign, function, loop, if, etc.
Custom syntax templates for each language
A web app with multiselect UI + ZIP bundling
Gumroad option to support or unlock everything ($5)
App + Source: https://townsendatomics.gumroad.com/l/usl
I’d love your thoughts on:
How it could be more useful for devs/teachers
Any language you'd want added
Whether this belongs as a CLI tool, VS Code plugin, or playground next
Happy to answer anything or collab. Thanks for reading!
I’m excited to share Universal Scripting Language (USL), a self-advancing interpreter that lets you run code from 466+ programming languages in one unified environment. It’s been a personal project for a while, and I’ve just uploaded it to GitHub for others to explore!
Key Features: Supports 466+ languages (and counting). Combines and executes code from multiple languages seamlessly. Open-source and extensible for your use cases. Why USL? Developers often struggle with combining tools and libraries across different programming languages. USL aims to solve that by providing a platform to execute and interact with these languages together. Whether you want to prototype, learn new languages, or integrate multiple languages into a single workflow, USL has you covered.
How to Get Started: Repo: Universal Scripting Language (GitHub) Clone the repo and follow the setup instructions. I’m working on improving documentation and creating a proper requirements.txt. I’m also writing an O’Reilly-style book on USL’s design and usage, so stay tuned for more updates!
I’d love to hear your thoughts, feedback, and ideas for improvement. Let me know if you’d like to contribute or collaborate.