This is a triumph. I’m making a note here, “HUGE SUCCESS”.

In recent git versions (>2.23), git restore and git restore --staged are the preferred ways to discard changes in the working tree (git checkout -- .) and staged changes (git reset --) respectively.

My point today is that, if we wish to count lines of code, we should not regard them as “lines produced” but as “lines spent”: the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger.

——On the cruelty of really teaching computing science - E.W. Djikstra

If you are looking at learning CS in a more holistic manner, there’s Path to a free self-taught education in Computer Science!. It’s a list of courses, categorized by topics, which are exactly what a CS undergraduate would learn. It might feel daunting at first, but you can pick any interesting topic and dive in.

I especially recommend CS50P for beginners.

One problem with exceptions is composability.

You have to rely on good and up-to-date documentation or you have to dig into the source code to figure out what exceptions are possible. For a lot of third party dependencies (which constitute a huge part of modern software), both can be missing.

Error type is a mitigation, but you are free to e.g. panic in Rust if you think the error is unrecoverable.

A third option is to have effect types like Koka, so that all possible exceptions (or effects) can be checked at type level. A similar approach can be observed in practical (read: non-academic) languages like Zig. It remains to be seen whether this style can be adopted by the mainstream.

For true immutability, burn something like tails on a read-only CD.

Ape together strong

Sean k strikes it again.

Yes for OCaml. Haskell’s inequality is defined as /= (for ≠). <> is usually the Monoid mappend operator (i.e. generalized binary concatenation).

Apart from cargo bikes, in London City ULEZ, buses, cabs, and utility trucks are allowed. It’s amazing how little traffic they generate.

It’s not that the author picked Rust for scripting. All Rust game engines (e.g. Bevy) use Rust as the scripting language.

Compare this with Godot, which is implemented in C++, but supports GDScript and many other languages for scripting.

Also, only supporting Rust is not considered a limitation, but a feature here. Bevy’s ECS is tied up with Rust’s trait system, therefore it’s impossible to use a different language.

So if Rust as a system programming language should not be used for game scripting, then projects like Bevy are fundamentally flawed. The author is willing to go there, but I don’t know if many people would go that far.

There could be a Godot-like engine written in Rust that supports easier scripting languages, but I think that space is not explored due to the fact that Godot already exists.

BitTorrent has partial seeding. So if someone extends a torrent with some files, the original one can still be used for seeding.

Another reason for the last bit being the slowest is because populars chunks are downloaded first.

according to McKinsey. “And for those Gen Zers who decide that driving just isn’t for them, they can keep themselves busy with TikTok in the passenger seat—or get behind the wheel in the metaverse.”

Be a good consumer and accept our thought control.

People who know monad: ???

People who don’t know monad: ???

What? Have you never been a streamee?

Good sound, good taste. - a Chinese proverb