V4N4D1SJan 31, 2024
Oh no.
Show threadDag Ågren ↙︎↙︎↙︎Jan 31, 2024

@V4N4D1S Don't get me started on how it is 20 fucking 24 and we still can NOT, under ANY CIRCUMSTANCES, put a PICTURE in a code comment.

Because clearly no code has ever needed a DIAGRAM to explain it. That would be utterly useless. Besides, it's not like computers could handle it.

Show threadHaelwenn /элвэн/ Feb 2, 2024
@WAHa_06x36 @V4N4D1S I'd say if your code needs an /inline/ diagram to explain it, your code is likely unreadable and so must be rewritten.

Documentation of the public API (which this one isn't) on the other hand could, which JavaDoc and similar ones tend to allow via rich-text/hypertext formatting.
Show threadDag Ågren ↙︎↙︎↙︎Feb 2, 2024
@lanodan Well, let me tell you from plentiful personal experience, that is incorrect.
Show threadHaelwenn /элвэн/ 
@WAHa_06x36 Meanwhile the only time I had to document that much was because people reading it couldn't actually read code (And not as in they sometimes need a bit of help, which is fine, but as in doesn't even gets things like string vs. integer vs. float).
Feb 2, 2024 at 3:50pmWeb
Show threadDag Ågren ↙︎↙︎↙︎Feb 2, 2024
@lanodan This is for documenting for myself.