base on Next-generation programming language that solves programmers' problems <div align="center"> <img src="./assets/logo/light_gradient.svg" alt="Nevalang logo"> </div> <div align="center" style="display:grid;place-items:center;"> <h1>Neva Programming Language</h1> <a href="https://trendshift.io/repositories/12825" target="_blank"><img src="https://trendshift.io/api/badge/repositories/12825" alt="nevalang%2Fneva | Trendshift" style="width: 250px; height: 55px;" width="250" height="55"/></a> [**Documentation**](./docs/README.md) | [**Examples**](./examples/) | [**Community**](#-community) | [**Releases**](https://github.com/nevalang/neva/releases) | [**Contributing**](./CONTRIBUTING.md) | [**Architecture**](./ARCHITECTURE.md)   [](https://goreportcard.com/report/github.com/nevalang/neva)  [](https://discord.gg/dmXbC79UuH) [](https://opensource.org/licenses/MIT)  [](https://chatgpt.com/g/g-RhZn00MXU-nevalang-expert) <p align="center"> <img src="./assets/animations/dataflow.gif" alt="Dataflow"> </p> </div> > ⚠️ WARNING: This project is under active development and not yet production-ready! ## 🤔 What Is Nevalang? Nevalang is a new kind of programming language where instead of writing step-by-step instructions, you create networks where data flows between nodes as immutable messages, with everything running in parallel by default. After type-checking, your program is compiled into machine code and can be distributed as a single executable with zero dependencies. Neva excels at stream processing and concurrency while remaining simple and enjoyable for general development. Future updates will add visual programming and Go interop to enable gradual adoption. ### Why Yet Another Programming Language? We created it because we saw a gap in the programming language landscape: 1. **Visual Programming Done Right** - existing visual tools are limited to specific domains or lack the power of traditional programming languages. Neva is designed from the ground up to be a hybrid visual/textual programming language. 2. **Simple Parallelism** - Most languages treat concurrency as an advanced feature. In Neva, parallelism is the default and it prevents issues like data races. 3. **Modern Developer Experience** - We combine best ideas from modern languages with dataflow paradigm to make programming easy and fun. Finally, exploring new programming paradigms helps advance the field by discovering what works and what doesn't! ## 👋 Hello, World! ```neva import { fmt } def Main(start any) (stop any) { println fmt.Println<string> panic Panic --- :start -> 'Hello, World!' -> println println:err -> panic println:res -> :stop } ``` What's happening here: - `import { fmt }` loads fmt package for printing - `def Main(start any) (stop any) {...}` defines component with input port start and output port stop, both of type any (it's safe since they used as signals) - `println fmt.Println<string>` defines a node, instance of fmt.Println - `panic Panic` defines another node to crash the program - `:start -> 'Hello, World!' -> println` defines a connection that sends the string to println when the program starts - `println:err -> panic` handles the possible error by crashing the program - `println:res -> :stop` terminates the program after successful printing > Runtime sends a message to `Main:start` at startup and waits for `Main:stop` to terminate ## 🔥 Features - **Dataflow Programming** - Write programs as message-passing graphs - **Implicit Parallelism** - Everything is parallel by default, no async-await/threads/goroutines/etc. - **Strong Static Typing** - Robust type system with generics and pattern-matching - **Machine Code Compilation** - Compile for any Go-supported platform, including WASM - **Stream Processing** - Handle real-time data with streams as first class citizens - **Advanced Error Handling** - Errors as values with `?` operator to avoid boilerplate - **Functional Patterns** - Immutability and higher-order components - **Dependency Injection** - Modularity with interfaces and DI - **Minimal Core** - Simple language with limited abstractions - **Package Manager** - Publish packages by pushing a git-tag - **Garbage Collection** - Automatic memory management using Go's low-latency GC - **Visual Programming** (WIP): Edit programs as visual graphs - **Go Interoperability** (WIP): Call Go from Neva and Neva from Go - **NextGen Debugging** (WIP): Observe execution in realtime and intercept messages on the fly ## 🧐 Why Use Neva? Let's compare Neva with Go. We could compare it to any language but Go is a simple reference since Neva is written in Go. | **Feature** | **Neva** | **Go** | | ------------------------ | ------------------------------------------------------------------ | --------------------------------------------------------------------------------- | | **Paradigm** | Dataflow - nodes send and receive messages through connections | Control flow - execution moves through instructions step by step | | **Concurrency** | Implicit - everything is concurrent by default | Explicit - goroutines, channels, and mutexes | | **Error Handling** | Errors as values with `?` operator to avoid boilerplate | Errors as values with `if err != nil {}` boilerplate | | **Mutability** | Immutable - no variables and pointers; data races are not possible | Mutable - variables and pointers; programmer must avoid data races | | **Null Safety** | Yes - nil pointer dereference is impossible | No - nil pointer dereference is possible | | **Zero Values** | No zero values - everything must be explicitly initialized | Zero values by default - everything can be initialized implicitly | | **Subtyping** | Structural - types are equal by their shape | Nominal - types are equal by their name | | **Traceback** | Automatic - every message traces its path | Manual - programmer must explicitly wrap every error to add context | | **Dependency Injection** | Built-in - any component with dependency expects injection | Manual - programmer must create constructor function that takes dependencies | | **Stream Processing** | Native support with components like `Map/Filter/Reduce` | Programmer must manually implement dataflow patterns with goroutines and channels | ## 🏭 Architecture > This is a high-level overview. For a more detailed overview of the architecture, please see [ARCHITECTURE.md](./ARCHITECTURE.md) <div align="center"> ```mermaid flowchart LR source_code-->compiler-->|go_code| go_compiler subgraph compiler parser-->analyzer-->backend end go_compiler-->machine_code go_compiler-->wasm ``` </div> Nevalang compiles to dependency-free, human-readable Go code that uses goroutines and channels for message-passing with parallelism. The Go compiler then produces optimized platform-specific code for any supported platform. This approach gives our programs access to Go's production-grade runtime with an advanced scheduler, garbage collector, and battle-tested standard library. We stand on the shoulders of giants. ## ⭐️ Star History <p align="center"> <a href="https://star-history.com/#nevalang/neva&Timeline"> <picture> <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/svg?repos=nevalang/neva&type=Timeline&theme=dark" /> <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/svg?repos=nevalang/neva&type=Timeline" /> <img alt="Star History Chart" src="https://api.star-history.com/svg?repos=nevalang/neva&type=Timeline" /> </picture> </a> </p> ## 💭 What's Next? > ℹ️ We take development seriously but have limited time to keep everything current. Feel free to reach out on our social platforms with any questions! - [Documentation](./docs/README.md) - Install and learn the language basics - [Examples](./examples/) - Learn the language by small programs ### Community This is an ambitious project maintained by a small group of enthusiasts. Your support by **joining us** will show interest and motivate us to continue. [](https://discord.gg/dmXbC79UuH) [](https://t.me/+H1kRClL8ppI1MWJi) [](https://www.reddit.com/r/nevalang/) [](https://x.com/neva_language) ### Contributing 1. See [contributing](./CONTRIBUTING.md) and [architecture](./ARCHITECTURE.md) 2. Check out [roadmap](https://github.com/nevalang/neva/milestones?direction=asc&sort=due_date&state=open) and [kanban-board](https://github.com/orgs/nevalang/projects/2/views/3?filterQuery=) 3. Also please read our [CoC](./CODE_OF_CONDUCT.md) 4. Join [discord server](https://discord.gg/dmXbC79UuH) ### Support Please **give us a star ⭐️** to increase our chances of getting into GitHub trends - the more attention Nevalang gets, the higher our chances of actually making a difference. <p align="center"> <img src="./assets/animations/github_star.gif" alt="GitHub Star"> </p> Please **share this project** with your friends! Every share helps us reach more developers and grow our community. The more developers we reach, the more likely we are to build something truly revolutionary together. 🚀 <div align="center" style="display:grid;place-items:center;"> [](https://x.com/intent/tweet?text=Check%20out%20Nevalang%20on%20GitHub:%20https://github.com/nevalang/neva%20%23Programming%20%23DataFlow%20%23Concurrency) [](https://www.facebook.com/sharer/sharer.php?u=https://github.com/nevalang/neva) [](https://www.reddit.com/submit?title=Check%20out%20Nevalang%20on%20GitHub:%20https://github.com/nevalang/neva) [](https://t.me/share/url?url=https://github.com/nevalang/neva&text=Check%20out%20Nevalang%20on%20GitHub) [](https://wa.me/?text=Check%20out%20Nevalang%20on%20GitHub:%20https://github.com/nevalang/neva) [](https://news.ycombinator.com/submitlink?u=https://github.com/nevalang/neva&t=Nevalang:%20Next-generation%20programming%20language%20with%20implicit%20parallelism) [](https://www.linkedin.com/sharing/share-offsite/?url=https://github.com/nevalang/neva) </div> ", Assign "at most 3 tags" to the expected json: {"id":"12825","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"