wheybags
Joined 10 years ago
Joined 10 years ago
Source: I have a bike with one coaster brake and one normal one. Have never intentionally used the coaster brake, have used it unintentionally many times.
1000 years red-washing.
Combine that with actual hard performance constraints, and if you're a "normal" software dev casually browsing some game code, it can be shocking (eg Celeste movement code: https://github.com/NoelFB/Celeste/blob/master/Source/Player/...).
Except the size of the blocked section ofc. E.g If you know it's a person's name, from a fixed list of people, well "Huckleberry" and "Tom" are very different lengths.
Modern compilers are bloated as hell huge things which makes it a bit impractical, but if it was a normal thing to do then we'd probably have optimized the binary sizes somewhat.
I just really like the idea of including _everything_ you need for the project. Also ensures that weird problems like this dont happen. As an extra benefit, if you included the compiler source and a bootstrapping path instead of just the latest binary, then you could easily include project specific compiler / language extensions with no extra effort.
I spent approximately as much time on building the word list as I did developing the game. The author's technique of just grabbing a word list and spellchecking it is completely not sufficient, you will get so many weird unfamiliar words in there. In the end I was able to whittle down my list to about 24,000 using various automatic methods, but from that point I just had to do a manual review on the remaining list, which meant I got to see a lot of words, and many of them felt very obscure and/or not fun.
1: shameless plug: https://wheybags.com/turntiles
It probably is, he's just probably using MacOS, where both long and long long are 64 bit. https://www.intel.com/content/www/us/en/developer/articles/t...
(that's the best linkable reference I could find, unfortunately).
I've run into a similar problem where an overload resolution for uint64_t was not being used when calling with a size_t because one was unsigned long and the other was unsigned long long, which are both 64 bit uints, but according to the compiler, they're different types.
This was a while ago so the details may be off, but the silly shape of the issue is correct.
Edit: maybe you could:
- remove outliers (anything that made the front page)
- normalise vote count by expected time in the first 20 posts of shownew, based on the posting rate at the time
Most interesting post is probably https://wheybags.com/blog/emperor.html