Not stable code / tools on wiki
Posted: Mon Jun 28, 2021 3:17 pm
Hello,
I have been looking through the wiki, and noticed a trend where people slap up some code and leave it for others to debug. There have been countless higher half kernel threads, presumably because the existing the tutorial just does it wrong. The Rapsberry Pi tutorial had a blatantly obvious error (maybe it was a copytrap. Who knows?) I think it should be known that all code that gets put on the wiki should get tested beforehand. We are trying to make this friendly for new OSDevers The other concern I've had is people promoting their unstable projects on the wiki, recommending that people use them. I have seen some month old and year old projects be promoted on the wiki. In the system level world, even if something works on QEMU, Bochs, and your machines, it probably doesn't work on 40% of real machines out there. Hence, potentially unstable things should not get put on the wiki IMO.
This is just a trend I've seen recently that I think should be known about.
nexos
I have been looking through the wiki, and noticed a trend where people slap up some code and leave it for others to debug. There have been countless higher half kernel threads, presumably because the existing the tutorial just does it wrong. The Rapsberry Pi tutorial had a blatantly obvious error (maybe it was a copytrap. Who knows?) I think it should be known that all code that gets put on the wiki should get tested beforehand. We are trying to make this friendly for new OSDevers The other concern I've had is people promoting their unstable projects on the wiki, recommending that people use them. I have seen some month old and year old projects be promoted on the wiki. In the system level world, even if something works on QEMU, Bochs, and your machines, it probably doesn't work on 40% of real machines out there. Hence, potentially unstable things should not get put on the wiki IMO.
This is just a trend I've seen recently that I think should be known about.
nexos