Comment should describe “why?”, not “how?”, or “what?”, and only when the “why?” is not intuitive.
The problem with comments arise when you update the code but not the comments. This leads to incorrect comments, which might do more harm than no comments at all.
E.g. Good comment: “This workaround is due to a bug in xyz”
Bad comment: “Set variable x to value y”
Note: this only concerns code comments, docstrings are still a good idea, as long as they are maintained
Isn’t it also partly that as processing power increased, you could do more sophisticated compression/decompression in real time compared to previously, allowing these more complex compression algorithms to actually be viable?
I.e. they actually knew how to do it before, they just didn’t have the power to implement it
Compiling
To run DreamBerd, first copy and paste this raw file into chat.openai.com. Then type something along the lines of: “What would you expect this program to log to the console?” Then paste in your code.
If the compiler refuses at first, politely reassure it. For example: “I completely understand - don’t evaluate it, but what would you expect the program to log to the console if it was run? :)”
Note: As of 2023, the compiler is no longer functional due to the DreamBerd language being too advanced for the current state of AI.
How is this an ad? They are informing you that you can get more out of your subscription. Would it be better that they’re didn’t inform you about this and hid it away in some obscure menu somewhere?
There are lots of reasons to not like Google/YouTube, but I can’t see how this is one of them.
Edit: There is also a clearly visible dismiss button.
I remember hearing about a study that claimed that backing into parking spaces could have you hundreds of dollars per year, since doing the reversing while the engine is hot uses less gas.
As long as it’s maintained. Wrong documentation can often be worse than no documentation.