Danacus

For me it’s overall much better on Linux now.

There’s a difference between consuming power to do stuff, and consuming power to charge. More power to charge = faster charging.

No, I phrased that poorly. What I meant is that if you have a struct that has some field (it owns that data), your operations on that data will be methods of that struct, and not some other struct that happens to have a reference to that struct. The latter is something people tend to do in OO languages like Java. In Rust, if a function accesses data, you usually “freshly” borrow from the owner of that data and pass it as argument to that function instead of relying on some “hidden” references somewhere in hidden in an object. Borrows will almost always be short-lived.

I don’t know if any of this makes sense, I’m sorry for the bad explanation. It might make more sense if you play with Rust yourself.

When you create an instance of a struct and assign it to a variable or field of another struct, that variable becomes the owner of that value. When you assign it to some other variable or pass it to a function that takes ownership, ownership will move. Otherwise, you will borrow. But there will always only be one owner for each value. That way you know exactly when to free up memory: whenever the owner is dropped.

You can store references in another structure, but you probably don’t want to do this most of the time, since it’s a major headache to get ownership and lifetimes right. You shouldn’t think of references as pointers, but you should think of them as “borrows”: you are temporarily borrowing something from the owner, but you can only do so if the owner exists. So you need to statically guarantee that for as long as you borrow it, the owner must be alive, which gets tricky when you store that borrow somewhere in some data structure. In practice, references or borrows will be short-lived, and most operations on data will be done by the owner of that data.

Underneath, references are represented by pointers, but you shouldn’t think of them as pointers, but rather as something you have borrowed, so in that sense it’s different from C.

Also, Python does use references everywhere, it’s just implicit, and depends on the type. Try storing a list in a class: you’ve just stored a reference to another structure. Most things (e.g. lists, objects) are passed and stored by reference, some types like integers are copied. In Rust, you can choose whether you want to pass by reference, copy or move ownership. At this point we’re still at a high level of abstraction, we don’t think so much about whether this will be pointers at the low level.

But my main point is that whether you use pointers, references, or whether it’s implicit or explicit doesn’t make a language slow or fast, it just defines how programs are written. Rust is very fast because it’s compiled to machine code and doesn’t do garbage collection or have any other overhead from a “runtime”. Python is relatively slow because it’s interpreted. You could argue that more manual control over references/pointers can make a language faster, but it’s not the main contributing factor.

I would argue that on the one hand you could say that the references to objects in garbage collected languages are also pointers.

On the other hand, you could argue that such references are not pointers, but then you might as well argue that references in rust are not pointers.

I just feel like “a language with pointers” is a weird way to describe a language and it isn’t really something that causes the language to become fast. Pointers are low level constructs that are used all the time, and whether or not they are abstracted away in the high level language doesn’t automatically make it slow or fast.

I’d say that it’s fast because it’s compiled to machine code and doesn’t use garbage collection. But I see what you mean with “pointer-based”.

Factorio

The cloudflare protection of their main instance is breaking federation right now, which is a bit annoying. I hope this will be resolved soon.

Jellyfin is free/open source software, while Plex is not.

Trackmania Turbo has never really had an active online community. The new Trackmania game called “Trackmania” is the most popular one, but you need to pay €10 each year to access most features.

I was already able to deploy it on my Raspberry PI 4 without any issues. It was using a lot of CPU when joining large rooms, but now it seems to have calmed down and it’s using 1-2% CPU, which is very reasonable. In comparison, home assistant runs at around 2-3% idle, and lemmy fluctuates between 4% and 10%.

Thanks for bringing this up, this is great! It’s also written in Rust, and I love Rust, so I might contribute this summer. I’ll add it to my list of potential project to contribute to, along with Lemmy.

I’ll blacklist them on my instance.

Conduit looks very interesting. Synapse is way too bloated to run and dendrite is way too buggy in my experience. Maybe conduit will become a better home server? I feel like the matrix devs just keep adding more and more features to their protocol, but they fail to implement usable servers and clients. IMO they should’ve kept things more simple.

Which Trackmania game? There are multiple, and some are more popular than others.

Trackmania! So many user made maps you never have to see the same map twice, and every map looks unique. You have a simple task: go from start to finish after collecting all checkpoints. Endlessly trying to get random bounces on “LOL” maps just never gets old.