On 10/15/21 5:13 AM, Michal Schorm wrote:
Thinking about this more, I always get to a question:
"Who are the consumers of that information and what do they actually
use it for?"
My personal idea is that the _ recommended _ requirements (of any OS)
are seeked by people that
1/ are going to install the system on some hardware on which that OS
wasn't previously present
2/ are looking up values with which they expect fluent, smooth,
experience both today and few year into the future
3/ _ want _ to install that OS, but have to purchase the HW yet, so
they are looking at recommendations on what HW to buy
The _ recommended _ HW requirements could be reviewed periodically
also based on the current market offering.
The market surely can differ through the world, as well as the average
purchase power.
However I wouldn't recommend anyone to e.g. go with less than 8GB of
RAM today, when considering what new HW to buy or what HW to use for a
setup intended to be used for years.
This is useful for development, however much RAM intensive work can be
done on the cloud or in some institutional settings a shared high
capacity local server. For most people, largest daily use would come
from spreadsheets and internet browsing. Many programs are sufficient on
4Gb of RAM, though many lightweight electron Javascript applications can
slow performance compared to similar C/C++/GO alternative applications.
Perhaps, we - as a community - might be able to gather our
expectations and make some average for those values?
The _ minimal _ requirements on the other hand are IMO seeked by an
entirely different group of people that
1/ are looking up the minimal requirements on recent HW for e.g. IOT
edition, or other use-cases in which you need to get the most of a not
really powerful but recent HW
2/ are looking up whether some HW from a XYZ years or decades ago
could run the Fedora Linux
Main issue is hardware security.
I understand it may be hard to check whether the HW meets the pure
technical limitations.
Though if we know how to do that, we may automate that and prepare
some package, some script purely for the purpose of this check. We
would also need to think about where to put it - the server edition
maybe, or the net installer, or could we patch the GRUB2 itself with
it, providing a custom call which could be selected as a separate boot
entry in all the bootable media we provide ?
What do you folks think - does the idea of defining the values based
on the use cases of people that are _ actually likely to seek those
values _ make sense as I tried to explain it?
It may be better to ask people using/developing different spins what
they find works for their spin. Bare OS is probably fine on 512MB - 1GB
of RAM. Applications and data used are more important - if you are
building software locally, doing image processing, video editing, doing
engineering simulation and design, doing communication, browsing the
web, gaming, or office applications, your needs will be quite different.
Possibly one can measure RAM use during CI tests for the applications.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
