Welcome to the forums.
Feel free to ask about programming in BASIC on Linux. A few keywords are supported only on Windows, unfortunately, but it's nothing to cry about. Make sure you check out the "Keyword of the Day" threads which always teaches something, especially the traps to get into. Don't pay a lot of attention to my posting on those threads... I mainly serve as "historian".
https://staging.qb64phoenix.com/forumdisplay.php?fid=49
One thing to remember is that the old INTERRUPTS aren't supported on WindowsXP and later systems, and a few things are emulated from 16-bit "conventional memory" and from input and output ports. It's not recommended to try to read the mouse with INTERRUPTS because QB64(PE) has had dedicated functions to do that for a while. Old programs still run which make use of those EGA "bit planes" but it's not recommended to start new programs with that technique. It isn't necessary because 32-bit color is supported, with transparency. This goes way beyond "SCREEN 13" supported by Q(uick)BASIC. A screen could be as large as you care to make it and you have enough RAM, but better off the screen if it's too large to display. Instead of "GET" and "PUT" arrays, screens could be set up according to your liking or your loading of sprites, then placed on the screen with "_PUTIMAGE", which supports flipping and stretching.
It only scratches the surface. There is a lot of information to take in but don't try to do it all in one day! Just relax and try your hand at programming in QB64(PE), and if you have a question, come back here to ask it without worrying about feeling like newton-born.
Feel free to ask about programming in BASIC on Linux. A few keywords are supported only on Windows, unfortunately, but it's nothing to cry about. Make sure you check out the "Keyword of the Day" threads which always teaches something, especially the traps to get into. Don't pay a lot of attention to my posting on those threads... I mainly serve as "historian".
https://staging.qb64phoenix.com/forumdisplay.php?fid=49
One thing to remember is that the old INTERRUPTS aren't supported on WindowsXP and later systems, and a few things are emulated from 16-bit "conventional memory" and from input and output ports. It's not recommended to try to read the mouse with INTERRUPTS because QB64(PE) has had dedicated functions to do that for a while. Old programs still run which make use of those EGA "bit planes" but it's not recommended to start new programs with that technique. It isn't necessary because 32-bit color is supported, with transparency. This goes way beyond "SCREEN 13" supported by Q(uick)BASIC. A screen could be as large as you care to make it and you have enough RAM, but better off the screen if it's too large to display. Instead of "GET" and "PUT" arrays, screens could be set up according to your liking or your loading of sprites, then placed on the screen with "_PUTIMAGE", which supports flipping and stretching.
It only scratches the surface. There is a lot of information to take in but don't try to do it all in one day! Just relax and try your hand at programming in QB64(PE), and if you have a question, come back here to ask it without worrying about feeling like newton-born.