If you don't know yet, I HATE <span class="explain" title="and all variants">Wikicode</span>. No offense to anyone, but I hate it with a vengeance. Personally, I'd much rather just be able to use HTML and CSS. Bulbapedia isn't bad with its support of HTML, but it would be much easier if it would parse for the img and a tags instead of automatically linking them. No, what really gets me are the sites that support ONLY <span class="explain" title="and all varaints">Wikicode</span>, nothing else. I can't blame Bulbapedia for supporting Wikicode, as non-coders are more likely to get interested in learning HTML and related languages. And now for some reasons that I hate <span class="explain" title="and all varaints">Wikicode</span>:

+

If you don't know yet, I HATE <span class="explain" title="and all variants">Wikicode</span>. No offense to anyone, but I hate it with a vengeance. Personally, I'd much rather just be able to use HTML and CSS. Bulbapedia isn't bad with its support of HTML, but it would be much easier if it would parse for the img and a tags instead of automatically linking them. No, what really gets me are the sites that support ONLY <span class="explain" title="and all varaints">Wikicode</span>, nothing else. I can't blame Bulbapedia for supporting Wikicode, as non-coders are more likely to get interested in learning HTML and related languages. And now for some reasons that I hate <span class="explain" title="and all variants">Wikicode</span>:

<ul>

<ul>

<li>Much too simple and text-oriented, makes it messy and confusing.</li>

<li>Much too simple and text-oriented, makes it messy and confusing.</li>

Contents

HTML

Being a very basic language with only limited improvement area, I have completed the language of HTML. Of course, I got some help from W3Schools, with the best web-based languages tutorials there are. I have learned some neat techniques though, and they work with CSS and JavaScript.

CSS

CSS, although the easiest web-based language to learn, is probably the hardest one to implement. There are pages upon pages of CSS handiwork that defies what you thought you could do. Some very common ones are cross-browser rounded edges, drop-down menus, and dynamic style alteration. CSS is one of my favorite languages to use, because there's a property and value for every situation. Even if there isn't one that exactly fits your needs, there's always a combination of two or more that works just as good or better.

JavaScript

As far as I dive into the pool of Object-Oriented languages, I never find another one like JavaScript. I can say, and others can back me up, that JavaScript is one of the most difficult languages to learn. There are two ways to learn JavaScript, the easy shallow way, and the mind-crushingly in-depth way. For a long time, I threw my best effort at learning it, becoming steadily more frustrated in my failures. After a while though, I got the hang of it. Not only that, but I began to feel that I could solve any problem I faced myself with. JavaScript is one of the most versatile languages that I have ever had the pleasure of failing at. In the end, though, when you finally understand it, JavaScript is best thing you will ever have done for your website.

DarkBASIC

My very first programming language. It's extremely user-friendly, but sometimes I just get frustrated because of how very easy it is. It takes so long to write that by the time that you're ready to go to bed, you've barely written anything! The very worst part, however, is that it doesn't use curly brackets ({}). This may seem like something cool at first, but eventually it really wears you down. While you may hate curly brackets because they yell and scream at you when you don't close them right, that's exactly the thing that makes me love them. When curly brackets disappear, so does the orderly structure in your programs. It blows up in the end. The end.

But, enough about computers for now...

Please, enough about programming and whatnot. Let's get to my current team:

And yes, I hate Wikicode so bad that I coded this entire team by hand from scratch in HTML. And now for the section on it:

Grr, Wikicode...

If you don't know yet, I HATE Wikicode. No offense to anyone, but I hate it with a vengeance. Personally, I'd much rather just be able to use HTML and CSS. Bulbapedia isn't bad with its support of HTML, but it would be much easier if it would parse for the img and a tags instead of automatically linking them. No, what really gets me are the sites that support ONLY Wikicode, nothing else. I can't blame Bulbapedia for supporting Wikicode, as non-coders are more likely to get interested in learning HTML and related languages. And now for some reasons that I hate Wikicode:

Much too simple and text-oriented, makes it messy and confusing.

No tags, makes the organization of elements much too hard.

Element declarations are not even remotely similar, making it impossible to easily tell the difference between tags and text.

Why in the world would people make an entirely new language to replace HTML, when it's completely unnecessary?

Wikicode is far less versatile than HTML.

The end.

BEWARE THE GTS!

Seriously, you aren't a Pokémon trainer if you have even one of the Pokémon on your team from the GTS (unless you have a pretty good excuse!). The reason is that people often put stuff on the GTS for cheap because they don't want it anymore. The sole purpose of them putting something up for trade is to get something better than what they gave. Think about it: if you put something up on the GTS, you're expecting to get more back than what you gave. Therefore, the entire GTS has collapsed into the Global Crap Exchange. So, to pull it all together, because all Pokémon you get off of the GTS will be crap, if you have a Pokémon from the GTS on your team, then that Pokémon is a piece of crap taking up a slot that could be used for a perfectly OK Pokémon.

Why we can't have Bug types, but we wish we could:

There are quite a few reasons why we all wish we could have a bug type, but sadly most of them are too horrible to use commercially. Of course, there are a few exceptions: like Ninjask, Shuckle, Shedinja, Yanmega, and possibly Forrretress and Scizor. Much farther than that, there aren't many for obvious reasons rather then those used in special circumstances. Here's why most Bug Types stink:

Statistically low stats.

Bad type combinations.

Weak to a starter Pokémon type.

And here's what makes six of them good:

The ability Speed Boost.

The ability Wonder Guard.

Almost all Steel types are good.

Bug types are usually unexpected.

So, the only reasonable conclusion to come to is that Bug types stink, but they would be great to use if there were more than six of them.