Notices by Ryan (aer@freeradical.zone)

@pluralistic As a sicko, I use an advanced tool called "rsync" to deploy "html files" from my "git repo"

@tek Ha, getting towards the end of the article, I was thinking "I think I would use a HashMap", only for him to mention that

Definitely didn't make the ECS connection, even having used a bit of Bevy. I hadn't considered using an ECS outside of game design but it makes a lot of sense

@tek Oh awesome, thanks

Yeah coming from a dotnet/python background I definitely tend to structure my code this way, and Ruts (and systems code in general) is way less amenable to it, for good reasons

Definitely a shift in the way of thinking

Wrote a dinky little multithreaded chat server in Tokio, wasn't too hard.

I did it using standard mutex/lock code to learn how it works, but typically prefer lockless code using pipes / actors. I think it suits the way I think about problems better, even if it is an abstraction

It did make me wonder something about Rust, specifically how to avoid copies

Mainly, my "database" is just a bunch of hashmaps in a struct. HashMap<i32, User>, HashMap<String, Room> etc

What I don't get is, how do I implement a get_user function such that it returns a read-only reference to a User, as opposed to a cloned User object?

I keep running into scoping/lifetime issues, and I get it. Realistically my Storage struct has a static lifetime, so it /should/ be fine, but the compiler doesn't know that

Do I have to return an Rc?

You don't have to put question marks after "I wonder" statements, and probably shouldn't

"I wonder" is a way of phrasing a question as a statement, and adding the question mark implies an interrogative tone that sound weird in context

The Kansas vote to ban puberty blockers just failed because of a 78-vote margin Democratic victory in the 2022 district elections.

I don't care if they suck. Vote for them anyway, because the alternative is worse and real. Your moral highground will lead to real life harm.

@thomasfuchs

Fortunately the model is always learning