Future of Vintlang: What design direction should we take?

[tacheraSasi]

Hey everyone,

I want to open up a forward-looking discussion about the future design of Vintlang. Since we’re still early, this is the best time to lock in a direction that will guide the language, its compiler, and ecosystem.

Some core questions we need to decide on:

1. Language Paradigm

Do we want to lean strongly into systems programming (like Go/Rust/C)?

Or a general-purpose scripting language (like Python/JS)?

Should we aim for a hybrid (safe systems + scripting-level productivity)?

2. Type System

Static typing with generics (Rust/Go/TypeScript style)?

Dynamic typing with gradual types (Python/TypeScript style)?

Should we design it for safety guarantees (memory safety, concurrency safety)?

3. Memory Model & Runtime

Garbage-collected (Go, Java)?

Manual / ownership-based (Rust)?

Hybrid approaches?

4. Concurrency Model

CSP / Goroutine-style (Go)?

Actor model (Erlang/Akka)?

Async/await (JavaScript, Rust)?

5. Ecosystem & Tooling

Should we start with a package manager like Cargo/NPM?

What about an LSP (Language Server Protocol) for editors?

6. Philosophy / Tagline

What’s the one-liner that defines Vintlang’s purpose? Examples:

“A safe and fast language for modern systems.”

“Go’s simplicity meets Rust’s safety.”

“The productivity of Python, the performance of C.”

[tacheraSasi]

Vintlang should be a compiled, statically typed language with modern concurrency, minimal runtime, and simplicity-first design (inspired by Go, but with some of Rust’s guarantees).

But I want to hear from you all — what do you think the future design should look like?

[Jeccoman]

LGTM