C# is like Microsoft-branded java. No real difference in the language, but some of the tooling for java is worse.

That’s just basically looking up the answer. … i will not learn anything from it.

Looking up the answer is the way to do it. You’re of course supposed to pay at some attention instead of copy-pasting without using your brains. As you keep doing things, you’ll develop a rough idea of how things are done.

Even if i find it (which is unlikely without asking an llm)

But i don’t know how i did it, and i couldn’t recreate it by myself.

You mean building the thing without any reference? Except for the most basics, you’re not supposed to memorize everything by the smallest details. Imagine asking a lawyer to know the details of every single law off the top of their head.

Seriously, go build that clock.

With basically no knowledge?

Well yeah. You find yourself some simple project and try to build it. When you don’t know how to do something, you look it up.

Like, make a command line clock, for example. Figure out how to get the current time, and then how to print it. And after that how to make it print the time once a second.

Edit: probably the most important skill in programming is breaking the problem into smaller pieces that you can then figure out. With experience, getting stuck like this becomes much less of a problem.

If you want to call it a fault. One instance can’t cover all, just the slice its users interact with.

Blaze screenshotted it at lemmy.ml.

The number shown is how many posts or comments your instance is aware of. If your number is smaller than the real one, it means that there’s content that doesn’t exist on your instance.

The missing content is either:

• Old: The account is like 3 or 4 years older tham your instance. Old content doesn’t get federated unless someone deliberately asks for it.
• Posted in communities that no one at your instance has subscribed to them yet. This stuff also doesn’t get auto-federated.

I was vaguely aware that some ancient architectures had weird byte widths, but I did not know about this. Pretty interesting.

This paper cannot succeed without mentioning the PDP-10 (though noting that PDP-11 has 8-bit bytes), and the fact that some DSPs have 24-bit or 32-bit words treated as “bytes.” These architectures made sense in their era, where word sizes varied and the notion of a byte wasn’t standardized. Today, nearly every general-purpose and embedded system adheres to the 8-bit byte model. The question isn’t whether there are still architectures where bytes aren’t 8-bits (there are!) but whether these care about modern C++… and whether modern C++ cares about them.

I’m fine with python, because it’s consistent. In C I get nervous every time I see it.

goto fail;