suggestions for future QB64

[DSMan195276]

So, for anyone is reading this, the takeaway from me is: 
* native support for arrays inside UDTs and 
* a native dictionary or associative array 
* HTTP/HTTPS

FWIW @mnrvovrfc, I currently work on QB64 and think all of these are great suggestions Built-in HTTP/HTTPS support is one of the things I'm currently working on and I've made some pretty good progress. Arrays in UDTs and built-in support for some other data structures is something else that I think is desperately needed (if for nothing else, to improve the code of QB64 itself). I think many of madscijr's other suggestions are also quite good.

Are all of them going to happen soon, or ever? Absolutely not We're a pretty small team (and any help at all is appreciated). But I think I can speak for all of us who work on QB64 in saying that we _do_ want suggestions like this, that's the only way for us to know what features people think QB64 is currently lacking and get a sense for what the most common feature requests are. Obviously if someone is demanding we do something then yes that's a problem, but madscijr's comments aren't even close to that.

Edit: I'll also add I agree with madscijr's general idea around what the purpose of BASIC is. QB64 is already a perfectly capable language, you can certainly implement your own HTTP logic, your own dictionary, fake arrays in UDTs, etc. I and many other members have done that often But you really shouldn't have too, frequently these implementations tend to have bad limitations or usability issues, and for newcomers they create a fairly big barrier for what should be simple things. So that said I definitely think we wouldn't exclude new features from consideration just because it's technically possible to do them today.