Okay that's a win. YouTube wasn't sure for years if I'm 18+ or not and didn't bother me with some shit
PlexSheep
Ich fucking liebe Sprudel ich trinke den ganzen Tag nichts anderes Sprudel ist so gut ihr habt alle keine Ahnung HAHAHA
Exactly. I'm looking forward to forgejo federation.
Selfhosted ci works well, but the GitHub ci is so fast it's not even funny. At least compared to my selfhosted stuff which is arguably cheap
Not all actions run on it.
Also, GitHub infrastructure is free and really performance, that's why I use it even if I have my own for server.
Also, discoverability. For the projects that I want to show to the world, GitHub is best, since it's most likely people see it there.
I have never watched a single star trek thing and the only knowledge I have about it comes from you guy's memes
Its one of the two hard problems of computer science after all
I found the study: https://doi.org/10.1145/3551349.3559494
It's open access, short, and really well written. Was a primary source of my bachelor's thesis.
Figure 2 for the lazy people:


The results of this study suggest that rust programs can be a bit slower, or nearly match the performance of C programs on x86-64, and that the runtime checks play a big role in this dynamic.
It's things like out of bounds checking. I'll go look for the paper and make another reply.
I have read papers for my bachelor's thesis that compared rust and c on x86-64 in terms of performance. It showed that C is a little or significantly faster, depending on the type of workload.
This is likely due to some runtime checks the rust compiler adds, and modified rust compilers that added less runtime checks led to about the same performance.
However, the performance is still very good for both languages (native machine code being executed), and in the same order of magnitude.
My own measurements for the armv6m architecture with an STM-32 showed that rust may even be faster in some cases, since the optimizing of the rust compiler was better, at least for that setup and for the CRC-32 algorithm.
I guess we'll need ratelimiting