[riot-notifications] [RIOT-OS/RIOT] doc/rdm: RFC - design goals (#10162)

danpetry notifications at github.com
Wed Jan 30 10:58:12 CET 2019

danpetry commented on this pull request.

> +
+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

The sentiment that I've picked up is that this is a real discussion - for example, people have cited the comments of one of the speakers at the last Summit that our key differentiator is that we have a slimmer memory footprint than the competition and that we should continue to strengthen that aspect. That to me is not at all artificial (if I understand correctly what you meant by the word).  

Re the language - to make it more tight - perhaps "with manual optimizations and specialized modules" -> "via configuration and modules that prioritize memory efficiency in their design, without of course departing from specifications". And delete the last sentence.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190130/2b99a285/attachment-0001.html>

More information about the notifications mailing list