>>1
I didn't write this kopipe, but oh so relevant:
You're doing it completely wrong. That's your problem. The last thing a programmer should do is take his language seriously (and you sound like you're doing that), because whatever language you're using, it's stupid. Some are less stupid than others, but the minute you assume that some feature of your language is more than an essentially arbitrary design decision, you're entering a world of hurt. This is especially true for e.g. Sepples, but even in well-designed languages WTFs abound.
You can laugh about it, or you can cry about it. It's up to you (you could also choose to develop an irrational emotional attachment to some language and pretend it's good. I advise against this). I'm going to laugh. You need to separate programming, which you presumably enjoy, from programming languages, which are fit only to be laughed at.
Programming languages (and hardware) are toys for you to play with, and nothing more. Programming today is like trying to build a car with Tinker Toys. Completely dismal if you think you're doing it in the best way and somehow you're just too dumb to make it easy. But a lot of fun if you realize you're taking totally inadequate materials and playing a hilarious game of "How good can I make these sticks look?" "What's the craziest thing I can do with totally inadequate materials?" Google for "rat bike". That's what you're doing.
Once you realize this you've got a leg up on all the SERIOUS BUSINESS faggots and on those who don't really enjoy programming. They may like it, and they may do it in their spare time. But unless they cackle with glee when they see something really neat, they don't enjoy programming. They just enjoy writing code, which is entirely different. Writing code is making something that works. It's about action. Programming is making it like it should be, staring in wonder at what thou hast wrought, then giggling at all the stupid things you did. Maybe you fix them, or maybe you let them be because it works and you've got another project to get to, but you know it's all a big joke. You code because you like to see code, and think you've got a neat idea. You see a program in your head, and you want it to BE.
Once you get in the right head space, nothing is worthless. Do I complain that I'm stuck writing Sepples in a stupid programming 2 class years below my level (lol switching majors)? No! I enjoy the chance to play with a strange (oh, so strange) new toy.
ITT: Satori. Listen the FUCK up, and you can be enlightened too. Also learn as much computing history as you can, read a bunch of EWDs, learn every language you hear about, and so on. Only by studying CS philosophy can you free yourself from the minutiae of computers and (our worst enemy) programming languages.