The blog post for Nim 2.0.0 RC1 used binary size measurements that were taken from the blog post for Nim 1.6.0 (2021-10-19). Update the data for Nim 2.0.0 RC1 (and RC2).
Also, mention -d:release rather than -d:danger. The referenced repo made that change for the first optimized build options. Rationale: we can save a few more KiB with -d:danger, but that's not worth giving any impression that "Nim binaries are only small in danger mode".
Avoid otherwise-inevitable comments of "yes, the Nim binary is smaller, but it isn't even safe".
The blog post for Nim 2.0.0 RC1 used binary size measurements that were taken from the blog post for Nim 1.6.0 (2021-10-19). Update the data for Nim 2.0.0 RC1 (and RC2).
Also, mention
-d:releaserather than-d:danger. The referenced repo made that change for the first optimized build options. Rationale: we can save a few more KiB with-d:danger, but that's not worth giving any impression that "Nim binaries are only small in danger mode".Avoid otherwise-inevitable comments of "yes, the Nim binary is smaller, but it isn't even safe".