I’m not sure if you read the post yet but I also have a short section about alternative notations which are less ambiguous or never ambiguous. RPN has the same issue as most notations that are never ambiguous namely that it’s hard to read - especially for big expressions.
Sorry for being a bit of a dick, I think you mean that the file “is 3.8MB”.
“mb” would mean millibit, 3.8millibit is an impossibly small file size, and would never exist practically (though I an sure that with some clever maths a zip bomb could be designed so that one bit of data could be compressed into 3.8millibits)
MB is the proper shorthand for MegaByte, a decent file size for a high quallity pucture, depending on the format and compression.
Unless we analyze the image, and determine the image format and compression settings we have no idea of if 3.8MB is a resonable size of the file or not, and the mods have hidden a rar file in the picture file, it is highly improbable that would be the case however.
While there are not actually any trailing commas in the dictionaries present and you are correct to say the ones present are part of a list, you can also have trailing commas in Python dictionaries. OP might have researched “Python trailing commas” and learned that part.
Trailing commas are fantastic to reduce changed lines in git diffs. Makes life much better. Same thing with leading commas in SQL queries.
At the very least, ai generated content needs to be clearly indicated. I have been surrounding things with the robot emoji, eg: “🤖ai content🤖”, whenever sharing something machine generated, and most people seem to be understanding what it means. Ai is here to stay, and many will use it for personal gain. We need at least some basic standards around the content so we can keep track of it.
programming.dev
Top