Going on program releases and worklogs, and other general comments by Mark, it's pretty easy to figure out what the future of Blitz most probably is.
I suspect three programs, Blitz+, Blitz3D, BlitzMax, all using a common compiler (so only one bunch of source for Mark to work with) and designed in a highly modular fashion.
Blitz+ will include standard modules, 2D and GUI, Blitz3D standard modules, 3D and 2D, and BlitzMax the lot.
Given his efforts with multiple graphics drivers on Blitz+, I would also suspect the graphics output itself is highly modular, meaning most APIs could be supported, probably with future cross-platform in mind.
Maplet is in some respects a test for the new Blitz compiler, which is why you won't see any updates for it for a while.
I would suspect Blitz3D development has slowed recently because it's hard to justify putting more effort into an old codebase.
I'm not associated with Blitz Research, just stating what I think is the logical direction Mark would take. Pinch of salt where necessary.
I suspect three programs, Blitz+, Blitz3D, BlitzMax, all using a common compiler (so only one bunch of source for Mark to work with) and designed in a highly modular fashion.
Blitz+ will include standard modules, 2D and GUI, Blitz3D standard modules, 3D and 2D, and BlitzMax the lot.
Given his efforts with multiple graphics drivers on Blitz+, I would also suspect the graphics output itself is highly modular, meaning most APIs could be supported, probably with future cross-platform in mind.
Maplet is in some respects a test for the new Blitz compiler, which is why you won't see any updates for it for a while.
I would suspect Blitz3D development has slowed recently because it's hard to justify putting more effort into an old codebase.
I'm not associated with Blitz Research, just stating what I think is the logical direction Mark would take. Pinch of salt where necessary.