Ma to kaj im piše da nepodržava rufus bi mogao biti danak premaloj razvojnoj ekipi pa se onda drze core job-a i nemaju vremena niti volje raditi bilo kaj van toga.
Nije rufus oduvjek imao u opcijama dd metodu. Cini mi se da se ta opcija pojavila tam negde sa hibridnim iso-ima. A to upozorenje na kaos webu mozda datira iz tog starijeg perioda ( prije uvodjenja dd u rufus ) , no jednostavno ili neznaju da sad to rufus može ili nemaju volje-vremena-kadrova to detaljno istestirati pa azurirati info...
Kaos ima vrlo usku i centraliziranu filozofiju i koncept pa se time i smanjuje mogućnost bugova, gresaka i sl :
Focus on one DE (KDE Plasma), one toolkit (Qt), one architecture (x86_64) plus a focus on evaluating and selecting the most suitable tools and applications.
All work is geared toward packaging, not developing new tools or applications. There is no goal to make the most possible software available, KaOS will stay limited in size of the repositories, and will work on quality instead of quantity. That goal makes it clear, a large user base is not what is intended or expected.
KaOS has limited repositories, for many users the options available will be plenty. When that is not the case, one of the reasons why Pacman was chosen for package manager comes into play. It offers about the easiest solution available to build your own packages. KaOS Community Packages (KCP) was created so everyone can share the PKGBUILDs they created or adjusted for KaOS.