nexos wrote: 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. Could be.
nexos wrote: The Rapsberry Pi tutorial had a blatantly obvious error (maybe it was a copytrap. Who knows?) If I recall correctly, I have been distracted by my little boy when I was writing that page, sorry about that. Wasn't bad for copytrap either BTW  As far as I know the Raspberry Pi Bare Bones page has been fixed several months ago, but if by any chance not, let me know.
nexos wrote: I think it should be known that all code that gets put on the wiki should get tested beforehand. As @iansjack said, if you volunteer for that, you'll get all the help from us. It's a noble and quite a big task to test EVERYTHING on the wiki.
nexos wrote: The other concern I've had is people promoting their unstable projects on the wiki, recommending that people use them. Agreed. I had the same concern about Limine, and removed it (causing a little fiasco because people didn't understand that unstable projects has no place on the wiki). I'm glad to see that it finally had a stable release and was put back on the wiki, however I still have concerns about how well tested it is.
nexos wrote: I have seen some month old and year old projects be promoted on the wiki. Agreed. For example I had issues with getting the tools for C#, because it lead to a dead link. (If I remember correctly has been fixed since, but still not sure if that old tool works with the latest toolchains. Maybe someone developing on Win can confirm that.)
nexos wrote: 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. I share your concern. I've spent years with a lot help from many many contributors to get BOOTBOOT tested on as many real machines as possible. I'd say this was a much bigger task than to write the loader itself, and I take the opportunity to say thanks to all contributors and testers here too. I'm still not convinced that Limine or BootProg for example has that kind of test coverage, but I better not edit their wiki pages because people wouldn't understand why I did it (not everybody share our concerns, keep that in mind). That being said I think they deserve a place on the wiki, we shouldn't remove them just because we're not sure how much testing their creators put in them, but we should distinguish untested software from tested ones somehow.
Cheers,
bzt
|
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.