7 ms·

If Rust is widely adopted, and if this commit adds a kilobyte to every language and every library downloaded by everyone, would the fun for the author be worth

• 4ad 12y ago
  Wow, a whole kilobyte! OMG. There are many valid reasons why this should be removed, but binary size is not one of them.
  • recursive 12y ago
    Why not?
  • jwatte 12y ago
    Can you do the math for me of every user on the internet times every program downloaded?
  • f4444 12y ago
    Size is certainly an important factor in embedded systems, one of the areas there is a lot of interest in Rust.
• ploxiln 12y ago
  If Rust is widely adopted, it'll save megabytes per executable compared to go or a nodejs tool with all its copies of all its modules. Really, the scale of efficiency delta between various things used on computers today is vast, and it's hard to say whether something like this "easter egg" is really significant. A few years ago I knew of a linux distro called "slitaz" that was a 30mb ISO, and it had x windows and a minimal window manager and a barebones browser and such.
  • mkishi 12y ago
    Genuine question: Megabytes compared to Go? Why?
    • untothebreach 12y ago
      Because the Go runtime is statically linked into every binary built by Go. This is nice for deployment, since you can just plop the binary onto any ol' server, but makes for large binaries.
• lclarkmichalek 12y ago
  yes
• ephemeralgomi 12y ago
  If Rust is widely adopted, and this actually becomes a problem for anyone, someone will submit a pull request to remove it, it will be debated, and probably pass. On the other hand, its presence in the current codebase will tend to attract playful tinkerers, which is arguably what it needs in its current stage of development.