this post was submitted on 16 Aug 2026
594 points (99.0% liked)
Open Source
48669 readers
786 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 7 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Performance matters a lot, because program can autosave in quick sessions after simple steps. Even more important if multiple images are edited or loaded. While this is not the biggest improvement, it is still something to keep in mind. Performance should always be a priority. Programs will keep expanding and add bloat over time, so its good to have a format like that in mind.
You should always measure first before blindly following dogmas. I doubt that the choice of serialization format is what dominates processor time in this case.
Then you follow it by doubting it without measuring:
Also note I was not just speaking of today, but with future additions and changes. You can't measure the future, but you can plan ahead and build upon a good foundation, that the small format can be used for extending it in future. That's the idea. Also to test what you suggest they have to build the entire system years and waste lot of time and effort.