_hyperscript VS awesome-rust

It seems to be this one:

https://github.com/bigskysoftware/_hyperscript

https://hyperscript.org/

but no sure it's anything to do with the OP though

You could help hyperscript get to a stable 1.0 by reading docs and writing up some use cases if you know anything about front end web development

If we returned from a function, we step out of it (discussed below). Otherwise, if the command returned a Promise, we await the next command, set cmd to it, notify the event bus and log it with some fancy styles. If the result was synchronous and is a HALT; we stop debugging (as I write this, I'm realizing I should've called continueExec() here). Finally, we commit the kind of code duplication hyperscript is meant to help you avoid, to handle a synchronous result.

It can be tricky to find learning resources that is perfectly tailored to the exact point we’re you’re standing right now. Especially if you already have prior experience.

But since you’re already familiar with programming, perhaps just dive right in…?

I.e. start a new project in Rust. You could do something like Advent of Code, Project Euler or Cryptopals[0]. Or write a simple webserver or whatever you feel like.

Don’t forget that ChatGPT can be quite useful for stuff like this. You can use it like a mentor. Just ask it anything you want to, make it show you examples (and then more examples) and so on. The answers might not be correct all of the time, but at least it can give you an idea of what docs to read next.

If you’re looking for blog posts, an acquaintance of mine has written some: https://priver.dev/tags/rust/

For more links to code/learning resources, see https://github.com/rust-unofficial/awesome-rust

And if you get stuck you also have the official Rust chats on Zulip/Discord.

HTH. Best of luck!

[0] https://cryptopals.com/

View on GitHub

I did find the official https://doc.rust-lang.org/book/ quite useful, it's more than enough to understand the language itself. Command-line programing is not a complicated thing, basically you have the CLI arguments, environment variables, stdin-stdout-sterr and nothing else. A few crates to start with: clap, dotenv, config, log4rs. Just go the crate documentation, there are many good examples there, no other book is neccessary. If you have a specific problem to solve, start to browse crates.io or https://github.com/rust-unofficial/awesome-rust for possible solutions.

37. Awesome Rust is a great repo with a huge curated list of plenty with Rust code and resources. You can find complete applications in different areas that were built based on Rust.

Post it there https://github.com/rust-unofficial/awesome-rust

I'd recommend taking a look at https://github.com/rust-unofficial/awesome-rust and seeing if anything interests you that way.

Not really sorted by complexity, but awesome-rust might be close to what you're looking for.

See also:

https://github.com/rust-unofficial/awesome-rust

This list is currently far more comprehensive, and it's filled with a lot of high-quality crates.