tav

Great work — the functional spin on top of Rebol's clean syntax is really nicely done!

Any chance you'll be adding something like the parse function? The ability to have domain-specific dialects was one of the best things about Rebol and would be great to see in a modern language.

And speaking of functions, could you make the "Function Reference" that's on the homepage, be available on a standalone page too? It's a very useful reference and would be great to access it easily. Thanks!

Over the last decade, Redis has been my go-to example of beautifully written code. Thank you for such an amazing creation @antirez, and best of luck for whatever you do next.

Could you elaborate on the "fundamental, serious limitations" by any chance?

In the off chance that some Rust developers are looking at this thread, I'd like to put forward a counter-proposal:

1. Use a postfix ?! instead of .await

2. Use a postfix ?? instead of .await?

3. Use the await keyword only in the "for await" construct

Then the common case becomes:

    let resp = http::get(url)??.to_string()

Which, imo, is a bit easier to parse than:

    let resp = http::get(url).await?.to_string()

This would make it easier to follow the core logic in async code, the same way that ? made error handling so much cleaner in Rust.

We'll be limiting it to open source projects — but not just software ones, whether it's an open hardware project, or an open source book, it'll all be welcome.

As someone who was a "child prodigy", people making a big deal of my age only made me feel good about myself and wanting to achieve more. Of course, this may not be a universal experience, but has certainly been common among the other child prodigies that I've since met.

Any chance the Smart Routing would be available as a TCP/UDP proxy service? It would be great to take advantage of Cloudflare's network without having to hand over your SSL keys.

This is the exact thing that I've been working on for the last year and a half. The biggest hurdle is actually handling the flow of money.

Because, unlike say Kickstarter/Patreon, where the money goes to a single entity/person, open source collaborations tend to be distributed and dynamic. So you effectively need to build a payments company and handle all of the headache that goes along with it.

But, having said that, I very much believe that something like this is needed — and thus why I'm still persevering with the project. Happy to chat further if cperciva/others are interested.