4 ms·
I was also concerned about the wasted overhead. However I guess it's just there for compatibility (since space is cheap) and for common encodings you'll be able
by snthpy 1y ago
I was also concerned about the wasted overhead. However I guess it's just there for compatibility (since space is cheap) and for common encodings you'll be able to skip reading it with range requests and use your trusted codec to decode the data. Smart move imho.
- nialse 1y agoI’m not concerned about the overhead, there is always more and larger pieces of iron. Still not a good idea to mix executable code with data.
- chme 1y agoIt really depends on the order of priorities. If the overall goal is to allow digital archeologist to make sense of some file they found, it would be prudent to give them some instructions on how it is decoded. I just hope that people will not just execute that code in an unconfined environment.
- nialse 1y agoHope is not an adequate security best practice. ;)