Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Red vs Lobster, the Slant community recommends Lobster for most people. In the question“What are the best (productivity-enhancing, well-designed, and concise, rather than just popular or time-tested) programming languages?” Lobster is ranked 26th while Red is ranked 57th. The most important reason people chose Lobster is:
Unlike Rust doesn't make the programmer jump through hoops, mainly automatic. Does an analysis similar to the Rust borrow checker to infer lifetimes, but makes life easier on the programmer.
Specs
Question Ranking
Pros
Pro Simple toolchain
Other languages have complex, multi-step setups that beginners often get stuck on. Red has no installer, no setup, no dependencies*, just a single small (~1MB) command-line executable with both the compiler and repl. On Windows, you don't even have to launch executable from the command line--it has a GUI-console.
Pro Very simple syntax
Red syntax is a lot like Rebol. It's easier than most languages for beginners to pick up.
Pro Both low and high-level
Red has low enough access to do systems programming, but it's expressive enough for high-level scripting.
Pro Low cognitive load
Red has very simple syntax that's easy to learn. It gets out of your way and lets you think about the problem instead, enhancing productivity.
Pro Compile time reference counting
Unlike Rust doesn't make the programmer jump through hoops, mainly automatic. Does an analysis similar to the Rust borrow checker to infer lifetimes, but makes life easier on the programmer.
Pro Python-esque syntax
There's an audience who loves that.
Pro WebAssembly backend
More options for users.
Pro Inline structs
Structs are allocated in their parent, and come at zero overhead.
Pro Automatic memory management
Better than Rust. No sadism.
Pro Type inference algorithm
Just works. Goes further than most languages in terms of allowing code without types.
Cons
Con Not production ready
Red is still under development and not considered stable.
Con Still in beta
It mostly works. It's good enough for building usable applications, but some planned features are missing.
Con Small community
Lead doesn't appear to be so ambitious or has a vision to push making more popular.
Con Compile time reference counting not 100%
Around 5% of time, need to escape to runtime reference counting. Working to get the percentage as low as possible.
Con Lobster not yet totally written in Lobster
Core written in C++. Plans to change that, but has been a long time.
Con Python-like syntax, but different use case and domain
Not Python compatible and often significantly different in purpose and use cases.
