I really do wish I had the time to write up a list of concise reasons as to why your post here serves absolutely no purpose other than to guide beginners down the terribly destructive path you've found yourself walking.
Unfortunately, or fortunately depending on how you look at it, I don't. Nor do I have the wherewithal or determination to invalidate everything you just spewed. No point in letting my time go to giving advice that slides in one ear and out the other, yet again and again and again. Ethin or visualstudio or someone else might have the patience to show you exactly where you went wrong for the 28th time, good on them or anyone else, but just so happens I don't. Which is probably why I don't do well teaching those who refuse to at least listen to advice voluntarily handed out by those more qualified.
Honestly man I think it would be a marvelous idea for you to stop, right now. Stop in your tracks and consider just what you're doing. Stop trying to teach others how to code when it looks as if you've barely mastered the basics yourself. You might think you're doing a good thing, but if responses around here are any indication this is sadly not the case.
Before you fly off the handle on the pretense that I don't know what I'm talking about because you've spent the last couple years working your ass off successfully making x and y and z in python and c++ and java and hell even x86 assembly, I want you to try taking a look at yourself through another, possibly unbiased lens.
You started out asking us to recommend languages, libraries, frameworks, resources and just about everything else. I mean that's fine. Annoying sort of, google does exist for a reason, but fine. I guess that's what we're here for.
then we go onto:
while(true)
{
The very next day you come back around asking the same sorts of questions. Most specifically what language should I choose? Oh what oh what should I do? Again, people come around to restate experience you should have just listened to the first time.
}
Still with me here? Good good.
Months later, you decide to write up some paragraphs containing a bunch of invalid claims that make little programatic sense. Point your browser over here if you'd like to see this same ol thing from the same ol guy once again.
Any programmer with the experience you claim to have should be able to shoot said claims about python out of the sky any day of the week.
Ethin and others actually take the time to do this. Not only are you unable to disprove 90% of his superior knowledge, you don't even try tackling the bulk of your numerous inconsistencies. In fact, here they are yet again. Just prettified with different words and dickishly arrogant sprinkling which I refuse to point out for reasons which should be obvious to everyone. Same shit, different day.
Oh yeah. The way you responded to Samtupy in post 11 is absolutely pathetic and I'd like you to take one good hard look at yourself before pulling any of these cards.
Sam_Tupy, Guy. First, learn to act independently. Learn to independently calculate formulas for the RotationPack, etc., and not use the tips of teachers.
Says the guy who finds it acceptable to pester devs day in and day out about the same sorts of things. Says the guy who took two years begging us to make your lifestyle and dev decisions.
You have been developing Redspot in Python for a year or more.
Uhh, nah. Very few people have inside info about the future of redspot development. Sam and myself are both in different summer independence programs right now. We plan to make it happen in the future... At some point. The both of us have many cool ideas and would love to see them through. Just not this second for a multitude of reasons. Ever hear of the great toy robbery? Oh shit? How about the yet to be released, but demoed, scramble or constant motion?
I could always turn this around on you. As the old proverb says, "those who live in glass houses should not throw stones." You've created next to nothing for the community to see or utilize as far as code.