QB Phoenix Edition name?

[Fifi]

Hello all.

You are doing an amazing and fabulous job bringing new life to QB64 by editing QB64 Phoenix Edition.

But just a suggestion/question: why continue to call it QB64 when simply QBPE would seem more appropriate and accurate to me?

Moreover, as I’ve read all the threads that talk about the various misadventures of the end of the QB64 project as such, calling this new fork by its new name including the name of its executable would:

• on the one hand avoid any new potential conflict with the alleged ‘’CEO’’,
  
• and on the other hand would also allow QBPE and QB64 to coexist on the same machine.
  

Moreover, this would avoid any possible future confusion for the users.

On my Linux boxes I did a test by changing only one line (line #90 EXE ?= qbpe) in the makefile and the two coexist very well, each in its own directory.

What do you think?

Cheers.
Fifi

[triggered]

It seems to me and my informants that renaming to QBPE has been the game plan all along, and this was originally slowed down by members who are conveniently not on this forum. While the project already effectively *is* renamed (i.e. choice of logo on the Wiki), all that really does is divorce itself from the QB64 legacy, not to mention its future. Many articles and books and websites reference QB64. It's been going on for years. The spinoff projects are all "QB64" compatible, as its baseline. QBPE is a spinoff. Also, the entire RC Cola / CEO thing is effectively a straw man. He's gone, that's over.

FWIW, you'll find steadfast representation of qb64 as a whole at qb64.com. Some of the old guard are still there helping in various ways, and that's with zero thanks to the PE sect, really.

[DSMan195276]

But just a suggestion/question: why continue to call it QB64 when simply QBPE would seem more appropriate and accurate to me?

Yeah I asked a similar question in a different thread I don't personally care all that much on the decision (QBPE, QB64PE, etc...), but I think the abbreviation needs to be agreed on as there's a few different ones being used at the moment. It also helps to make it clear which version you're talking about without having to spell out the whole name each time.

As for the exe, yes that's trivial to change the name of.

[Coolman]

personally, since the beginning of the creation of this forum and my registration, I recovered the archives and installed qb64 in a directory named qb64pe (version 0.5.0) then qb64pe-v082 for version 0.8.2. since this version will differ more and more from the original version, I think it should be named QB64Pe...

[RhoSigma]

I vote for QBPE, it's what's already used in our Forum/Wiki logos and what I use in the Wiki pages when clarifying the availability of certain commands.

[triggered]

Just as an aside, the word "phoenix" really came out of nowhere. The mythology of the word suggests that QB64 died, and was brought back personally by admin, or SMcNeill, or whatever. What happened in April was qb64.org got highjacked, and then in that power vacuum a few guys each bought qb64-related domains. I think qb64phoenix was simply cheaper than qb64.com, so that was chosen. Funny enough, several days later, the coveted qb64.com itself was purchased and will properly represent the characters Q-B-6-4 regardless of what happens here. It's mostly a sleight of hand that the forums landed here, but beware this is an island, there's more with qb64 going on out there.

[SMcNeill]

Just as an aside, the word "phoenix" really came out of nowhere. The mythology of the word suggests that QB64 died, and was brought back personally by admin, or SMcNeill, or whatever. What happened in April was qb64.org got highjacked, and then in that power vacuum a few guys each bought qb64-related domains. I think qb64phoenix was simply cheaper than qb64.com, so that was chosen. Funny enough, several days later, the coveted qb64.com itself was purchased and will properly represent the characters Q-B-6-4 regardless of what happens here. It's mostly a sleight of hand that the forums landed here, but beware this is an island, there's more with qb64 going on out there.

QB64.org never got hijacked.  The domain and all were handed over peacefully, and willingly, from Fellippe to RC Cola.  RC then decided to kill the project by shutting down the forums, wiki, twitter, youtube, and any other qb64.org related service which he owned and controlled.  He pulled the plug on everything and killed the QB64.org involvement with the project.

Phoenix Edition was born out of the ashes of that burned project and the name was chosen as a symbolic symbol of showing that even when one tries to kill us off, we'll simply rise again.  The forums here, and the domain qb64phoenix.com, was created on 4/16/2022.  QB64.com wasn't purchased until 4/26/2022, by a different party.  The servers were already set up here, and the working github was already established and had already released our first initial release to correct issues with the wiki and help files not downloading properly, by that time.  To take all the underlying architecture which had already been established and put into working order, and simply to uproot it to migrate over to someone else's domain name, wasn't an acceptable proposition.   We're interested in moving forward -- not sideways.  

As far as I know, there's no "power vacuum" with QB64.org, nor any of the other domains which branched off from that site after it collapsed.  RC Cola *still* controls QB64.org, the same as ever since Fellipee passed it over to him.  QB64.com has had leadership at the helm of it, ever since it was purchased by Cory, and QB64phoenix.com has a well structed development team with several people involved in various aspects of maintaining and improving the project.  Various versions have branched off into different directions, but each of those seem to have their own established leadership methods and none are suffering from a "power vacuum".

For Phoenix Edition, we have so far:

Swapped over to the newest compilers for Windows user.
Replaced the png image library with a version which is 30+% faster.
Moved over to a MakeFile set-up system.
Corrected several different bugs and issues that were in the source.
Swapped out the wiki, enhancing the look and design of it, as well as correcting the issues inside QB64 itself which freezes up the IDE when trying to connect to the old, now non-existent, site.
Added an option to compile to temp files which clean up after themselves after execution.
Added options to specify and change compiler settings and optimizations.
And several other things...

I think we're developing along nicely, and I hope everyone else feels the same as well. 

---

One thing to keep in mind with the name is the simple fact that we've *only* been up and running for about 2 months now, and we've been working on a ton of other things such as the highlights which I've listed above.  We've restored a set of forums.  Rebuilt the wiki, and rebuilt all its templates from scratch.  We've been working on the repo and sorting out any and all issues that we may have inherited from the version 2.0.2 versions and previously.  Swapping over the name, icon, and such, has been on our radar for a while now, but it definitely hasn't been a pressing issue.  We're still in the ZERO version numbers, and our discussions were set to decide what we wanted to do by the time we reach a version which we feel could be considered our first true *stable* release -- v1.0+.  Issues are still popping up with the new makefile system, and we're still sorting out some glitches that pop up from time to time from the old team's last version, so we've never actually bothered to do much more than just kick the idea around with the name "QBPE", while everyone was working on stuff they considered more important.

Honestly, I expect that by the time we get ready to hit version 1.0, we'll probably move directly onto "QBPE v3.0", or so, so that people will be able to tell that we're a version which was built off of, and expanded beyond, QB64 v2.02.

[RhoSigma]

Honestly, I expect that by the time we get ready to hit version 1.0, we'll probably move directly onto "QBPE v3.0", or so, so that people will be able to tell that we're a version which was built off of, and expanded beyond, QB64 v2.02.

+1

[triggered]

I don't have the patience to filibuster like SMcNeill does, but it seems like the recent and proposed updates to the PE compiler are comprised of (i) things that the old Team cautioned against, and finally they're gone, so SMcNeill can have fun, and (ii) creating change just for its own sake, simply to be different from QB64 legacy as fast as possible. If QB64 "moves forward", then I should look forward to using it on more devices, in cleverer ways, with more capacity to expand. This comment extends years backwards too: the Team was really just dancing around what Galleon handed them. All vertical movement with QB64 was done by Galleon, anything recent is horizontal. In fact, any improvement people keep making just further crystalize, further snuggle into the same rut. Micro optimization unto death. Grassroots spinoffs have a real shot at breaking the spaghetti ceiling.

BASIC will move forward in the browser, on mobile. The desktop is more of a specialized hobby tool, time to catch up.

[RhoSigma]

BASIC will move forward in the browser, on mobile. The desktop is more of a specialized hobby tool, time to catch up.

-100