I might be misunderstanding something, but it seems the issue isn't really about whether GET can technically carry a body. The deeper concern is that HTTP methods have specific meanings, and mixing those signals can causes confusion and it's nice to have this semantic separation.
If you want your database to just store bytes, use a key-value store. But SQL gives you schemas and constraints for a reason; they're guardrails for your business logic. Just don’t ask your tables to run the business for you.
"The new screen capture Wayland protocol has been merged! It will unlock neat features such as window capture and better performance. Many thanks to @andriyngvason for pushing this forward!"
I evaluate the quality of a goal using this criterion: if its opposite is nonsensical or foolish, it's not worthwhile. For example:
"Deliver the world's most advanced, safe, and responsible AI."
This is not a very aspiring goal that will distinguish you from your competition because why would anyone want to deliver the world's most outdated, unsafe and irresponsible AI?