How dare @[email protected] not reveal the address of the programmer instance.

* Swedish developer of the year

Don’t get me wrong, he does great work, but your post should mention it somewhere.

Rust doesn’t allow type inference in function signatures, c++ does with auto. IIRC, they recommended against using it, because of -you guessed it- compile time.

I know, but otherwise there is no use for the knowledge that we live in a simulation. Unless someone can contact the outside of course.

The only thing one could do with knowledge of being in a simulation, is trying to find bugs and exploits.
From now on, I expect anyone claiming we live in a simulation to have a working perpetual motion device, faster that light communication, or something similarly impressive. If they don’t, their claim is meaningless useless.

I’m sorry I don’t know all the arcane incantations of your court system of the top of my head.

And considering the content of the “comics”, one set up to glorify AGI as our lord and savior.

What would the defense say? “That wasn’t him, just someone who looks similar.”
They already claim that by pleading innocent at the start.

Should have gone with the rising star cave, with the homo naledi fossil location.

^^^^
This H. sapiens didn’t even italicize properly.

Es gibt eine Sargpflicht?
Wenn ich nicht Berliner wäre, würde ich in mein Testament schreiben, dass ich heimlich Muslim bin um keinen Lackholzkasten zu verbuddeln.

You could save 0.64 bit per char more if you actually treated you output as a binary number (using 6 bits per char) and didn’t go through the intermediary string (implicitly using base 100 at 6.64 bits per char).
This would also make your life easier by allowing bit manipulation to slice/move parts and reducing work for the processor because base 100 means integer divisions, and base 64 means bit shifts. If you want to go down the road of a “complicated” base use base 38 and get similar drawbacks as now, except only 5.25 bits per char.

Unless you only copy and compare you have to decode it, or implement more complicated logic for everything from searching to concatenation (which is normally just memcopy).

Ich bin mal regelmäßig an einem vorbei gefahren und habe ihn von ca. 200 bis über 500 wachsen sehen. Als ich später vorbei geschaut habe, zeigte er etwa 50.

The standard xkcd on making another thing:

https://xkcd.com/927

On frameworks specifically, I recommend the song:

We’re gonna build a framework,
cause we wanna use one,
but don’t wanna choose one

We’re gonna build a framework
We didn’t like the others,
So we’ll write another

I never understood why they don’t add just a little syntactic sugar. You don’t need much to take it from a mess of brackets to something comprehensible.

It was in the original design, but not the first implementation. By the time someone got around to it, people where used to S-expressions.

I can’t comment whether learning C first improves your rust, but it certainly makes you appreciate what the rust compiler does.
Also learning rust improved my C.

If an animal gets shot with lead, survives and runs away, there is now a wounded animal or an animal carcass containing lead somewhere in the wild.
If it is wounded or freshly dead a carnivore will eat it and accumulate lead. That may be large carnivore or a smaller carnivore that later gets eaten by a bigger one. Birds tend to have stronger stomach acid that most mammals, allowing them to dissolve the lead better.
Vultures having it the worst as they will eat any carcass and have the strongest acid.

https://youtu.be/CBv4bO_jC8I 27:09