this post was submitted on 29 Jul 2025
56 points (88.9% liked)
Programming
21924 readers
710 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's a very heavily gamed benchmark. The most frequent issues I've seen are:
They've finally started labelling stupid submissions with "contentious" labels at least, but not when this study was done.
They provide the specific implementations used here: https://github.com/greensoftwarelab/Energy-Languages
I dislike the "I thought of something that may be an issue therefore just dismiss all of the work without thinking" approach.
I agree, but if you take away the hard numbers from this (which you should) all you're left with is what we all already knew from experience: fast languages are more energy efficient, C, Rust, Go, Java etc. are fast; Python, Ruby etc. are super slow.
It doesn't add anything at all.
Well... No. You're reading the title. Read the document.
"We all know" is the gateway to ignorance. You need to test common knowledge to see if it's really true. Just assuming it is isn't knowledge, it's guessing.
Second - it's not always true:
Thirdly - they also did testing of memory usage to see if it was involved in energy usage.