11-06-2022, 05:42 PM
I didn't want to risk clogging "JavaScript-ing it, I need to get with it" with anything of no interest to anybody (or of interest and creating a whole discussion maybe not fitting the OP in that thread.
To me, every BASIC implementation out there that isn't "dead" is filling a place for however many folk that no other BASIC implementation can.
I can imagine that some folk might very well use one ore more BASIC implementations, each for one or more specific purposes.
Although both BAM and QBJS can outright stand on their own for what they are good at, I think both of them also have the potential of being great sidekick helpers for QB64/QB64PE/QBASIC (the big boys) programming.
If not 100% compatible with the big boys, then at least compatible enough for coding certain snippets of code. Why? To be able to create/edit those snippets of code from anywhere anytime (you just need a web browser), regardless of device and without an available install of "a big boy" BASIC.
This is a pretty big deal not just for anywhere-programming-anytime, but also for testing algorithms/functions/subroutines/whatever. You can put the code on the web not just for viewing the code, but also running it. That kind of world-wide access/availability means you can get collaboration from anywhere at any time easy peasy.
In my mind, QBJS and BAM are otherwise very different beasts. I think:
Just like neither QBJS nor BAM can ever be competition for QB64/QB64PE/QBASIC, QB64/QB64PE/QBASIC can never be competition for either QBJS or BAM, just like QBJS and BAM can never be competition to the other: all very different beasts really good at specific things.
QBJS and/or BAM as sidekicks for QB64/QB64PE/QBASIC for whatever projects? There is some bad-a$$ potential there.
To me, every BASIC implementation out there that isn't "dead" is filling a place for however many folk that no other BASIC implementation can.
I can imagine that some folk might very well use one ore more BASIC implementations, each for one or more specific purposes.
Although both BAM and QBJS can outright stand on their own for what they are good at, I think both of them also have the potential of being great sidekick helpers for QB64/QB64PE/QBASIC (the big boys) programming.
If not 100% compatible with the big boys, then at least compatible enough for coding certain snippets of code. Why? To be able to create/edit those snippets of code from anywhere anytime (you just need a web browser), regardless of device and without an available install of "a big boy" BASIC.
This is a pretty big deal not just for anywhere-programming-anytime, but also for testing algorithms/functions/subroutines/whatever. You can put the code on the web not just for viewing the code, but also running it. That kind of world-wide access/availability means you can get collaboration from anywhere at any time easy peasy.
In my mind, QBJS and BAM are otherwise very different beasts. I think:
- QBJS is and will be the cat's meow for compatibility and performance
- BAM is and will be the cat's meow for serious project management, source code management, and all things software development process, including documentation (being a TiddlyWiki instance, BAM inherits all of the core TiddlyWiki goodies, and the goodies from whatever TW plugin's get added as you make BAM your own)
Just like neither QBJS nor BAM can ever be competition for QB64/QB64PE/QBASIC, QB64/QB64PE/QBASIC can never be competition for either QBJS or BAM, just like QBJS and BAM can never be competition to the other: all very different beasts really good at specific things.
QBJS and/or BAM as sidekicks for QB64/QB64PE/QBASIC for whatever projects? There is some bad-a$$ potential there.