<p><b>@danpetry</b> commented on this pull request.</p>

<hr>

<p>In <a href="https://github.com/RIOT-OS/RIOT/pull/10162#discussion_r253041886">doc/memos/rdm-draft-petry-riot-design-goals.md</a>:</p>
<pre style='color:#555'>> +
+Modules outside the core should leverage the benefits and address the
+programming challenges of such a scheduler. They shouldn't demand that users do
+the same.  They should, however, allow users to manage power through different
+modes and functions.
+
+#### Small memory footprint
+
+Most of RIOT's targeted use cases are well addressed by devices in class 1 of
+the taxonomy presented in [1]. If small price differences are important or the
+energy budget is particularly tight, the available memory might be near the
+bottom of this class. Over-the-air updating currently reduces the available ROM
+by over half.
+
+RIOT should provide out-of-the-box support for devices with ~10 KiB of
+available RAM and ~100 KiB of ROM. It should be just as possible to address
</pre>
<p>I think being more specific is a good path. Would this be able to be directed further in a way which helps a RIOT kernel developer to judge how far they should optimize their new module for size? For example, we could angle it as a list of indicative sizes (+ size range, special cases, etc) for certain types of feature? And point out making available optimized libraries alongside more fully functional ones?</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/RIOT-OS/RIOT/pull/10162#discussion_r253041886">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AEn7YER3YJ1YRW_Oet5vVXkHOkFg2Gdnks5vJDszgaJpZM4Xb9Mj">mute the thread</a>.<img src="https://github.com/notifications/beacon/AEn7YLHqV1MnTlsmpH722I_vb_z0YCPcks5vJDszgaJpZM4Xb9Mj.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/RIOT-OS/RIOT","title":"RIOT-OS/RIOT","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/RIOT-OS/RIOT"}},"updates":{"snippets":[{"icon":"PERSON","message":"@danpetry commented on #10162"}],"action":{"name":"View Pull Request","url":"https://github.com/RIOT-OS/RIOT/pull/10162#discussion_r253041886"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/RIOT-OS/RIOT/pull/10162#discussion_r253041886",
"url": "https://github.com/RIOT-OS/RIOT/pull/10162#discussion_r253041886",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>