16,087 karma · joined January 4, 2011
contact at my-hn-username dot org
By default, this is only in debug mode. I recently forgot to add it to release mode on a project, and was surprised when I broke the CI (tests run in debug, I only tested in release mode).
> I solve and write a lot of puzzlehunts, and I wanted a better programming language to use to search word lists for words satisfying unusual constraints, such as, “Find all ten-letter words that contain each of the letters A, B, and C exactly once and that have the ninth letter K.”1 I have a folder of ten-line scripts of this kind, mostly Python, and I thought there was surely a better way to do this.
I'll chose to remember it was designed for AoC :-D
On mappers: this forget about 3rd party (non-sega) mappers like Codemasters' https://www.smspower.org/Development/Mappers
On resolution: the SMS can have a higher than 192 pixels vertical resolution: https://www.smspower.org/Development/Modes ; and some (Codemasters, again) games did use that: https://www.smspower.org/Tags/Extra-Height
On ROMs checksum verification: no need to guess, this is documented depending on the BIOS: https://www.smspower.org/Development/BIOSes
Nevertheless, I loved the comparison with Famicom's hardware design.
Last but not least, don't forget about sverx's devkitSMS for writing SG-1000, SMS or GG software: https://github.com/sverx/devkitSMS
https://fr.wikipedia.org/wiki/Trottoir_roulant_rapide#/media...
Basically: some managers gets fed-up with weeks/months of delays for baremetal or VM access -> takes risks and gets cloud services -> successful projects in less time -> gets promoted -> more cloud in the org.
> The Hopper H200 is 47.9 gigaflops per watt at FP64 (33.5 teraflops divided by 700 watts), and the Blackwell B200 is rated at 33.3 gigaflops per watt (40 teraflops divided by 1,200 watts). The Blackwell B300 has FP64 severely deprecated at 1.25 teraflops and burns 1,400 watts, which is 0.89 gigaflops per watt. (The B300 is really aimed at low precision AI inference.)
- pathogen in 2011
- vundle in 2013
- vim-plug in 2017
Haven't moved since, Plug still does the job, even after I moved to neovim in 2021. Will probably move to the new built-in package manager once the dust has settled.
Yet I'm still surprised by this benchmark. On both Zen2 and Zen4 in my tests (5900X from the article is Zen3), matrixprod still benefits from hyperthreading and scales a bit after all the physical cores are filled, unlike what the article results show.
All of this is tangential of course, as I'd tend to agree that CPU utilization% is just an imprecise metric and should only be used as a measure of "is something running".