60
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 09 Nov 2026
60 points (91.7% liked)
Programming
29290 readers
611 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 3 years ago
MODERATORS
There's absolutely a catch. You wrote that code for a single piece of hardware. You hand tuned it for that one specific platform taking advantage of every trick you could find. It probably took longer to write than your website and it didn't really matter if it wasn't perfect.
You can't buy a system that slow or that memory constrained anymore (spare me your weird embedded processors, you know what I mean). Move on.
The other catch is something OOP mentions right at the beginning: The main reason their app was 2MB large was because it had images.
You couldn't do full-frame images on a SNES. Instead, images were built up by pasting small sprites and repeating background tiles everywhere.
If you want high-res images with a colordepth of more than 13 colors per pixel, you will need a lot of storage space for that.