nynrathod

interesting one. Is it only available in mac? as rust can build cross platfrom binary? any plan for other os?

So does it calling api for all platfrom and you show all feed on you app? so user can customize what to see?

Great product visualization with code

Just one suggestion, instead of adding manual won't track the correct mood. What if it tracks auto as per our activity via work, my code, or agent work prompts all? That may result in the correct mood? may be long work but just a thoguth

I tried, but honestly, all end with lack of tool or configuration or hardware config. None of them work for me. At end paid apis only providing productivity else free local end with inveting time and less effecient work

Author here. Happy to answer questions!

What I'd love feedback on:

1. Is the @decorator syntax clear or confusing?

2. Would you use this for a real project?

3. What's the #1 missing feature?

Repo: https://github.com/nynrathod/doolang

Examples: https://github.com/nynrathod/doolang/tree/main/examples

Doo is a statically-typed, compiled programming language built in Rust + LLVM, designed for building production ready APIs quickly.

0.2.0 Alpha is the biggest update so far. It adds the core foundation for built-in methods, a stronger std library, file I/O, improved modules, error handling, enums, match, array features, map improvements, JSON support, and more.

Highlights

Built-in methods

- Array: len, push, pop, contains, first, last, reverse, isEmpty, clear, sort, slice, indexOf, map, filter, reduce, join - Map: has, remove, isEmpty, size, clear, keys, values - String: len, charAt, subString, toUpper, toLower, contains, startsWith, endsWith, trim, reverse, indexOf, replace, repeat, concat, charCode, countSubstr

Std library

- Array utils: Unique, Range, Sum, Average, MinArr, MaxArr - Math: Abs, Pow, Sqrt, Min, Max, Floor, Ceil, Round - File: Read, Write, Append, Exists, Delete, Size, MkDir, Metadata, ListDir, Copy, Move, ReadLines, RmDir, RmDirAll

Modules & language features

- Imports (namespace, wildcard, alias, inline) - Functions with tuple return, struct + JSON support - Error handling (T!E, ? operator, propagation, custom errors) - Structs with methods, nested structs, shorthand, enums inside structs - Enum types (scoped + inline) - match on primitives, struct, enum, nested match - JSON parse/stringify - Lambda + chained array methods - Inline if/else, ternary in expressions - Array spread, ranges ([...arr], [1..4], [1..=4]) - Improved map iteration - typeOf, cast operators, ++/-- - UTF-8 print

Examples folder => https://github.com/nynrathod/doolang/tree/main/examples

The goal is to keep Doo simple but practical: something you can use to build real APIs or tools quickly without a huge language surface or runtime complexity.

If anyone here enjoys language design, I'd love feedback. It's still early alpha, and I'm very open to feedback. If anything feels weird, confusing, too limited, or too magical, please tell me, I want to shape this based on real developer expectations, not just my preferences.

THanks for sharing, will take a look surely, as memroy mgmt will be crucial for doolang. And I can see you are valgrind developer?

Interesting will take a look in this point, thanks for sharing

Good point, will remove that word, btw will added unsigned float in upcoming release. Thanks for that comment.

Hi everyone,

I launched doo: Simple Fast and Secure compiled programming language written in rust+LLVM.

My Idea is to have simplicity to write server apis with minimalist and clean syntax. Not started as hobby project but I wanna grow this.

I got many feedback and suggestions here https://news.ycombinator.com/item?id=45797044 that I need some specific feature for doolang or have to turn this in unique product. But I don't have any buzzing idea or feature except minimalist and clean syntax with speed and security for writing server apis where compiler may do behind the scene magic to have high level syntax without any compromise.

What do you think, any idea or suggestion to turn dooalng any domain specific language or any killing unique feature or anything that make doolang its place? My intensions is not to replace any existing language. I will release built in methods and std library in upcoming release, so its just staring of doolang yet, after it will add more test cases and memory test and bug fixes more. And http router is next planned after those.

Any suggestions from community will be valuable.

True, it takes years. And as a solo dev its really hard. Turning into product really makes sense, i understood now i need something unique or specific feature. but as of now only writing apis routers and server with super simple syntax with speed and security only having in my mind. but I value your point, do you have any suggestions or recommendations? I'm also thinking to start new post to take ideas and suggestion from community.

Hi, thanks for pointing this out. Yeah struct and enum are alredy in pipeline. memroy mgmt and codegen work pending for those 2. Planning to release in 0.3.0 but let me see if possible on next release of 0.2.0

Struct enums are base of any type safe language will surely add in upcoming releases.

Doolang i started for writing server and apis easily and simply, but you points make sense for Wasm components. Not planned as of now as this is just starting point, but surely would take you thought for my further roadmap. Honestly i'm not too much expert in such thing yet, but would appreciate if you have any other more recommendations and suggestions

Thanks for valuable feedback. Yeah definitely will add more examples projects.

And really make sense your point to have usp or any unique or good feature doolang should have. As this is just starting point of doolang, and honestly i never started this as hobby project I want this to be mature over years not to replace any languge but to have simplicity for writing servers and apis. after few months I will definitely integrate this with my own production note taking app once i improve this language.

Reference counting i Introduce for auto memroy mgmt only, as rust ownership and borrow method will be extreme complex to implement as solo dev i feel.

But now im clear now language should have any special feature or target which is lacking, idk what to find for this, but it will be valuable if you can suggest, im also thinking to have new post to ask feedback from community what they want in such language. Any suggestion?

Thanks for pointing that out. I didn’t actually know all the details about how Valgrind works under the hood just that it does memory checking. I'll definitely read up more on it. If you have any good resources or tips, I'd appreciate your suggestions!

Doolang currently does not allow you to mutate a primitive variable from another function.

Only support this as of now

fn Foo(x: Int) { x = 123; // Only modifies Foo's local copy print("inside Foo", x); // Print 123 } fn main() { let x: Int = 0; Foo(x); // x is still 0 here after Foo returns print("out x", x); // Print 0 }

But your points make sense, i should learn those UB works and will check how its behaving

Doolang aims for memory safety with static typing and automatic reference counting, so you won't see classic C/C++ bugs. But it does not claim Rust's level of safety there’s no formal guarantee that safe code can't cause undefined behavior. It's quite safe in practice, just not as strict as Rust.

For complex types (strings, arrays, maps), values are reference-counted and passed by reference. If you pass such a value to a function, you're sharing the same object—mutations affect the original. For primitives (Int, Bool), it's pass-by-value (copy).

Saying safe will be too early, but design philosophy is no compromise with security and speed with easy syntax. It passed with 550+ test cases including unit test, memory stress, integration, circular dep, regresssion, valgrind memory leak, fuzz testing, also i added conservative limits max depth for recursion and data length for stability. Find here https://github.com/nynrathod/doolang/blob/main/src/limits.rs

Doolang not uses any traits like rust. Rust is great language, but its expose everything in syntax that is also great but as developer who want security+speed with fast development may found issue writing rust, that is main goal of doolang simlicity. I'm still figuring out further design principle of syntax to have less exposing syntax.

Doolang have auto memory management with reference counting. Just simple mut keyword introduced for mutating variable let mut data = "data"; no other syntax expose all handling automatic with rc and auto type define if not defined explicitly

Hi,

Yeah make sense, but I don't have any buzzing goal right now, doolang is not any dsl, just to ensure high level syntax for developer writing backend servers apis. And not started as learning project. Will move forward as per feedback of community and requirement but not such specific target im aiming. so again simple concept is keep it simple to write with speed and security

Hi,

So main goal of this language is to have simplicity while writing code. Rust is great will dominate, but as dev who want speed and security but with high level syntax, doolang is best for them. Right now im working on std library and inbuilt function, and moving forward I will integrate doolang with my own note taking app uoozer note https://play.google.com/store/apps/details?id=com.uoozer.not... , 550+ test cases covered by doolang already with valgrind memroy test too.

so for roadmap, after inbuilt functions and standard library deployment will build http router and will test real world scenario for api dev. IF all well then will integrate with uoozer note.