Yeah, I spent a lot of time ensuring the website would load quickly and I do away with a lot of "optional" cruft.
There's no Javascript full stop, no stylesheets (all CSS is embedded in each page) and every page load is a single web request (with the exception of the screenshots page).
Even the SVG logo is embedded in the pages!
Writing it this way also causes each page to be self contained, a download of the HTML page includes all of the CSS, logo and information so it can easily be saved and viewed locally. :)
> The only remark I have regarding code quality is that the word splitting warning is disabled for the entirety of kiss: I would have disabled it on a per-occurence basis.
There are 8 occurrences of word splitting in the source, each and every one is intentional.
I also enable all lint errors when working on the package manager itself (to catch any unintentional word splitting which may slip through my fingers).
The ideal goal is to reduce the word splitting count to zero though! :)
(I'll go ahead and make the change you're suggesting until I do remove all word splitting).
You don't need to install another Linux distribution beforehand, you just need to boot another distribution's live-iso to partition disks and download/unpack KISS.
This is simpler on my side as I don't have to compile and package a heavy kernel, generate an initramfs, build a squashfs and finally package it into an ISO image.
On the user side this enables more flexibility too. You can use a live-iso offering a GUI for "easier" partitioning or an iso in which you _know_ includes the firmware you need for the installation process etc.
The download for KISS is only a 45MB~ tarball and the installation is just unpacking it to your newly partitioned disk at `/`!
This also allows for the same installation tarball to double as a working chroot in existing systems. In my eyes, this method is simpler all round.
You can download the installation tarball, extract it to a directory and use 'chroot' to start tinkering with it. The installation tarball doubles as a working 'chroot' image. :)
That'd be really nice and it is something I've thought about, the issue is figuring out the _right_ way to do it. Self publishing or perhaps a publisher of programming books?
I can see now that there's a clear interest in a release in physical form. I'll start seriously looking into it. :)