Because, as I said, I don't like to write games in C. I like to write other stuff in C, just not games.
Fair enough, you don't like that tool for that job.
 Well, I'm not going to make it completely easy. That would just be another BASIC clone. I think Classes, trash collection, inline assembly, etc would be a good addition to the traditional BASIC language. But, newbies wouldn't have to use those features if they didn't want to. By "limiting", I was speaking in terms of the feature set.
Agreed, beginner developers would not need to use the more advanced features. But to create anything really deep, you would need to use those features. You can make it easier to interface with low level operations, agreed. I just don't see why you don't create a C++ class to do that for you, instead of an entirely new language. But, as you said, you don't like using C to program games in.
 When I'm writing a game, I like to think from the design side. C/C++ is just not the language for me when I try to make a game. If I had something simple, yet powerful, I'm sure making games would be a lot easier for me.
From what you are saying, it sounds as if you are an experienced programmer, expecially if you are willing to takle creating a new language(with the feature set you have described). So, why are you finding it so difficult programming in C/C++ for games? What makes a game so much harder than other apps you have written? The design side should be very code non specific. You should never even talk about what language you are going to use in your game design. The eventual implementation of your design will have tons to do with C++, not the creating of the design itself.
About my time... honestly, I have a ton of it. I've been thinking for the last 3 days about something I should work on. A compiler finally popped into my head and I decided to give it a try. Besides, who says you have to use it? Or anyone else? I'm really making it for my benefit because I think it would help me in the long run. If other people like it and want to use it, more power to them. When you say it's a waste of time, you're speaking from your point of view. But, here's the thing... you're not making the compiler. I am. So, it's really up to me whether it's a waste of time or not.
Agreed, it is your time, you can do with it as you please. But you also asked on a forum what people though of your idea, your time. Don't ask if you don't want answers. I don't think I was being rude in saying I thought it was a waste of time given your target goals, which is game programming, not tools programming(from the information you provided). If you indeed do feel that you are more interested in programming a language than go for it, it sounds like a great challange, and a blast. But if your goal is to program games? Then no, this is not worth your time.
I do not agree that making a language too powerful will make it complex, on the contrary. Making a powerful script language is all about removing the low-level stuff from the user, and make simpler high-level interfaces that they can use instead.
From what I gathered he wasn't talking about a simple scripting language, he was talking a fully featured programming language, his feature set seemed to indicate that as well. As I said above yea, you can reduce the complexity by making higher level interfaces to low level stuff, but in the end, your going to need to do more than basic read and writes, especially when it comes to games programming. Like inline assembly, he wants that, how is that easier in his proposed language than in C++?
Cypher, in the end, it comes down to, do you want to program games right now, or later? If you want to program games right now, then this is a waste of your time, as you won't be programming games for quite a while(going under the assumption this is a fully featured language, not just a limited feature set scripting language). If you can wait, and you really like the idea of your proposed language, then go for it, it sounds like it would be a good time.