Project link: https://github.com/helix-editor/helix

A list of what to do after reading the rust book

A good docker image boilerplate

A simple server to create a webring

It handles CSS grid and flexbox

These are relevant arguments in favor of Go.

The state of the art CSS parser and minifier.

This tool is used by Mozilla for Firefox.

“It lets me write multi-headed programs that run on 16 cores and keep them readable, maintainable, and crash-free. It also lets me write low-level algorithms requiring control over memory layout and pull in a crate that makes HTTPS requests super simple. It’s the combination of these features that makes Rust so unique.”

And the feedback from Github on the language.

you reminded me in this episode of the day that someone published a crate named "nul" which made it so no one on Windows could use any crates

"error: [20/-1] Cannot checkout to invalid path '3/n/nul'" LOL

To solve XDG misconfiguration, if wanted.

Even after applying various default filters and providing a GUI to search and filter the remarks, there is still a lot of data to go through.

Understanding the remarks is quite challenging. What even is FastISelFailure or SpillReloadCopies? How can I change my Rust code to resolve these remarks? Hard to say if you’re not a LLVM expert.

A rust malicious postgress package was used to retrieve information and send it to a secret Telegram channel.

The rust foundation and crates.io removed the package.

The tool install binaries directly. It can be especially useful for CI (or maybe Raspberry Pi).