the future for FreeBASIC should be graphics and games development, not GUI.
FreeBasic has gradually become a multi-specialty language. How would functions oriented towards game development be contrary to the use of a GUI? I have nothing against thinking that the future of FB could be graphics and games, why not, but what bothers me is that it should only be that and nothing else, like if the truth was to restrain language. I understand that it is a "noble" part mathematically speaking, and also that it is a hard and competitive issue requiring advanced means and skills. No one is preventing you. I believe in ease, in the greatest accessibility, but with possibilities of scalar complexity, in RAD but RAD with scalar complexity. It is for these reasons that I mentioned TinyDialog in my previous post, precisely to underline the fact that even GUIs are too complicated and that easy to use and offbeat products can arouse, in a relevant context (ie handling quick and easy), developer interest, and finding an audience. As Marcov so aptly puts it, RAD requires solid objects. To make them efficient you need expertise, knowledge, work and talent, or as you prefer time, sweat and headaches. The contexts do not compete with each other (except those actually in duplicates, like 15 different GUIs but without real distinctive originality, yes), the different contexts enrich each other. The purpose of these contexts is to enrich the language and not to enclose it in an increasingly targeted expertise and in a narrow field of application and ultimately incapable of competing with anything else. I think you are both right and wrong. Reason for wanting graphics and games, but wrong to believe that the other fields of application will change to become graphics and games at your convenience: they will not change, they will not strengthen, they will pass out.