Monkey is for MoonScript

N is for Node.js

O is for Objective-C

P is for Pascal

Q is for QBasic

R is for R

S is for Swift

T is for TypeScript

U is for …

Fix it now, or you go to jail

chmod +x virus
sudo ./virus

I like the description by a Finn who said: Rust is like a car with automatic, while in C (or Zig) you need to change the gears.

I don’t think this metaphor is correct. The automatic gear’s analogy would be the Garbage Collector, which almost every mainstream language has. Rust’s memory management, in comparison, is still manual. Maybe not as manual as C or Zig - but I’d say about as manual as C++. The difference is not that it has some weird gear-changing (memory cleanup) scheme that does not require human intervention - it’s that it yells at you when you don’t do the regular gear changing (memory management) properly.

My condolences

Certainly not for running an LLM on all your files to figure out which ads to show you in the start menu. Why would you even imply something like that?

Why are you asking? Are you trying to prematurely optimize these apps?

I want to forget SVN

Hard drive was made by Tesla

Ah, yes. A private method for working on a public field.

Doesn’t MS Access still use SQL?

All government data is processed using sed.

My code is portable enough to support all versions.

No. You need to run it in a VM that runs TempleOS.

You’ll need my fork of docker, and you’ll need to apply a patch.

My website only works with Chrome, but it has to be a specific old version of it. And you also need to install some extensions. Very specific versions of these extensions. Few of them already removed from the store due to security backdoors.

I have a Docker image you can use to run Chrome though.

The other four distros they use are Lubuntu, Xubuntu, Gobuntu and Mythbuntu.

Why use print! and not println!? You’ll just mess up the terminal text flow…

From a certain point of view - isn’t this exactly what happened here?

I often go into a Git worktree of one of my projects and mess around a bit to try something out. If I find it’s not working, I tell git to discard the changes with git checkout . and git clean -df. What I’m saying is exactly “on second thought, don’t do anything" - while what happens in practice is that Git restores all files to their HEAD status and removes all the new files that are not already in HEAD.

Of course, the difference is that I already have all the work I want to keep under source control, so these changes I’ve discarded really were that - just changes. He, on the other hand, “was just playing with the source control option” - so these “changes” he was discarding really were all his work. But Git did not know that.

Downvoting in order to bring it below @whynot’s comment.