Questionnaire results

written by Tomas M. 2 years ago

After getting over 1250 responses to the Questionnaire published month ago, I should be able to make some conclusions. I'll describe them here.

1. Slax language translations

More than 65% of users prefer to use Slax in English only. Some users reported they voted for non-english support only because of their need to use non-US keyboard layout, which seems reasonable. So as a conclusion, taking into consideration the fact that creating and distributing 40 language mutations is a headache, I've decided that if there is a new Slax release, it will support non-US keyboard layouts, but will not provide localized translations - those should be available only as modules.

2. Slax base - keeping Slackware?

Almost 84% of all respondents do not care if Slax is based on Slackware. This means that I can do practically anything when selecting the base for Slax. To be honest I didn't decide yet if I want to switch. The problem with Slackware is that there is no way to get extra software easily. I am considering Debian and Gentoo at the moment.

3. Slax size

Only 5% of users prefer Slax to keep <200MB size. And 63% of users can accept size over 500MB. So I think targetting to ~500MB or ~700MB (to fit a regular CD) may be the best decision. I think 700MB is not such a deal nowadays. If I can put more data on file, it will mean less work for me optimizing the size.

4. Graphical desktop

Only 4% of Slax users prefer console-only OS, so graphical desktop will remain included. Only 10% of users would appreciate Gnome3. The rest of users is divided almost equally to three groups, one requesting very lightweight desktop like OpenBox, another one liking KDE, and third one appreciating desktop like XFCE. This basically mean that whatever I do, I'll piss of most users :) and it also means I can do whatever I like :) I did not decide yet. So I think that I'll select something lightweight which looks like KDE :)

5. Slax Architecture

Keeping Slax in several architectures is lots of work. I suggested a solution in one of the previous blog posts, I was thinking about the possibility to include both 32bit and 64bit kernels (appropriate kernel would load automatically) while providing only 32bit userspace binaries. This looks to me like the easiest way to make Slax working on all x86 architectures without any drawbacks. So for now I like this idea.

6. Applications in Slax and Download Format

Those questions were mostly informative for me, so I could see what's most important for users.

7. Modules

Modules are core of Slax. Only 17% of users do not care about modules, other users need them, either to create their own stuff or to (at least) download stuff built by others. I think the number would decrease if Slax was built on, say, Debian, since people could apt-get instead of downloading modules from the repository. In all cases, I see I have to keep the modularity.

Tomas M.

(c) 2019, Tomas M; rss