wkk

Just fork it 🤓

It definitely feels like a knee jerk reaction, but there would be some merit to it: The Rust language feels apt to implement a kernel with. If I remember correctly that’s what Redox is trying to accomplish? https://redox-os.org/

Antagonizing the borrow checker is wrong. If it screams it does so to prevent you from writing a mistake. Eventually once you have enough experience you should write code in such a way that doesn’t trip the borrow checker because you know how to properly handle your references.

Is it difficult to learn at first? Yes, but the benefits of learning this outweighs the downsides such as writing code that may use references when it shouldn’t.

I’m not a Rust aficionado, but the few Rust I’ve written opened my eyes on issues that I have been dealing with in other languages but for which I was blind.

Lastly I tried following a Godot project tutorial that was using GDScript except I challenged myself to follow it but rewrite the examples given using Rust’s bindings for Godot. It was definitely more cumbersome to work with, but I might also have been doing something wrong (such as blindly transcribing GDscript instead of writing more idiomatic Rust).

All of that to say 1) borrow checker is your friend and 2) scripting languages will always be more convenient at the cost of being way more dirty (way less safeties)

In the end you need to pick the right tool for the job. Multiple tools may be used within the same project.

https://www.khanacademy.org/computing/computers-and-internet/xcae6f4a7ff015e7d:the-internet/xcae6f4a7ff015e7d:routing-with-redundancy/a/internet-routing

I wouldn’t call that “messy and inefficient” but you do you. I’d be curious to know what’s a “clean and efficient” solution for you when it comes to routing packets around the planet :)

It’s important to look at the dockerhub page to see the available tags (I usually prefer smaller images like alpine)

The usage docs for the docker image should be in the dockerhub readme.

But the first result to the query docker redis image should be the dockerhub entry, followed maybe by blog posts and tutorials.

Otherwise you can query something like redis doc or redis docker tutorial.

With such a query the first expected result would be https://hub.docker.com/_/redis, and then blog posts if really that’s what you want.

On my device I cannot find a link to dockerhub at all with the same query.

You may not be a developer, but the first expected result with that query would be a link to https://hub.docker.com/_/redis

Google is really bad at this for some reason and will point you to blogs that as a dev I don’t care in the slightest. Hell, using the same query I cannot find a single link to dockerhub on my device, it’s extremely frustrating

Technically speaking it would pick up the men in metal armors, not the wooden horse per se.

But the barrier would lift for the wooden horse full of men in armor indeed.