Talk:Protecting Memory Secrets: Difference between revisions

Content added Content deleted
Line 52: Line 52:


Worse, from a rosettacode point of view (worse partially because the approach outlined here can assist in the creation of plausible looking garbage), the fact that there is no "task" here, means that there's no way for us to compare implementations, let along judge the viability of any claims about implementations for the general case. (We might judge in the context of specific machines, but without intimate knowledge of the machine architecture we'll have difficulty even there.) --[[User:Rdm|Rdm]] ([[User talk:Rdm|talk]]) 03:31, 13 January 2023 (UTC)
Worse, from a rosettacode point of view (worse partially because the approach outlined here can assist in the creation of plausible looking garbage), the fact that there is no "task" here, means that there's no way for us to compare implementations, let along judge the viability of any claims about implementations for the general case. (We might judge in the context of specific machines, but without intimate knowledge of the machine architecture we'll have difficulty even there.) --[[User:Rdm|Rdm]] ([[User talk:Rdm|talk]]) 03:31, 13 January 2023 (UTC)


=== Disagree, Task is valid ===

* There are development security standards that make this a requirement. Whether you or I or anyone else agrees with the approach is mute. Whether or not there is a better way is also mute.
* As for several ways to complete the task, I could easily create 3, 4, or 8 separate tasks for this. I don't think that really helps anyone.
* Mixing in plausible garbage is just one approach.
* Pointing to language documentation is a valid part of a task. Documentation is part of programming and reference documentation is also a part. It may not be the most fun part but it's valid.
* If people don't like the task, they don't need to try it.

[[User:EnigmaticC|EnigmaticC]] ([[User talk:EnigmaticC|talk]]) 01:44, 15 January 2023 (UTC)