10-31-2022, 07:40 PM
(10-31-2022, 06:09 PM)bearheathen Wrote: And that's the saddest part. I see the value of BOTH. I see advantage in being able to reach the Old School and New audiences. I myself fall somewhere in the middle. I daresay this may well apply to a large portion of potential users.
Restore the wiki...AND have it available in Github Markdown. Is it extra work? Sure, but there are adherents of both philosophies who are clearly willing to make the effort and the information is made more widely available. That is an advantage, I would say.
And one of the nice things about this hobby/profession/craft is its flexibility. It is entirely possible to have a fully modernized repo with full CI and automation...while also having a simple ZIP hosted on a page. Again...you merely cater to the widest possible audience when MORE choice is offered.
First, I will point out that PE does have a modernized repo with a CI process that runs tests on every build and PR, and automation to create releases and CI builds. We also have a growing test suite, a new build system that has allowed us to greatly improve the quality of the new code we've added/replaced and start on cleaning up the existing code, and many other things that you can see on our GitHub.
As for GitHub markdown, I've played with it and even built a process to directly pull the contents of the qb64phoenix.com wiki into GitHub. Unfortunately the result is just not good. The issue is less "why not duplicate it" and more "why create a duplicate which is just inferior to the real one and requires an extra automated process, which can break, to keep it up-to-date?". As a back-up it's fine, but frankly as a primary source for people to use it's not great for a wiki as large as QB64s. I'm not saying MediaWiki is the best, but I haven't yet seen someone propose something that's actually better (and worth our limited time to look into).
(10-31-2022, 06:50 PM)bearheathen Wrote: There has GOT to be a way to fix it. As a technician and developer, I firmly believe that nothing is so broken that it cannot be fixed. What would it take to bring the geniuses on both sides back to the same table?
I get that, it does suck for someone who just wants to use QB64. But then, why should I, someone who's been working hard on PE (along with many others) to turn in into something much better than before, basically throw that all away just to meet Cory's list of nebulous demands and start developing his version in the way he wants with only the changes he wants? A list, I might add, that includes many of the things _we've already done_ in PE and he has ignored.