Hi!
@Spyda
Thank you for your reply. With the domain transfer charges being the same as the domain registration charge, I think the best course of action would be to let the domain registration expire and then re-register it instead of transferring it, as anwii suggested in his message further up (earlier) in this thread. The risk involved with such a 'modus operandi' is that somebody could just come along and steal the domain name while it's between expired and registered with the new hosting service. Another potential problem is that some domain registration services hang on to an expired domain name for a while in the hope that you would renew it with them - it's probably one way for them to make sure that you do not switch over to another domain registration service, especially if they don't respond to requests to release the domain without charging a fee since the domain is expired.
BTW, I've looked at the reviews for several web hosting companies at
http://www.web-hosting-top.com and most web masters complain about the hosting firms taking away their services when they start getting a considerable amount of traffic. Although there are some cases in which the hosting providers are really ripping off web masters, it may also be because the CPU load from a script is high. Running WordPress on a shared hosting server without any form of caching is asking for trouble - it generates a really heavy CPU load! The folks at StackOverflow.com probably got their feet wet when they initially switched to the WordPress blogging platform and as they weren't really aware of the concept of WordPress-caching, their CPU usage went sky-high and they dubbed WordPress as the destroyer of CPUs. They later figured out the caching bit, but not without putting up their share of slander/libel with their blog post for their bad experience resulting from their own ignorance.
The problem of a heavy CPU load is pretty common among PHP scripts, but if you use them for prototyping, building intranet websites, or for a custom application (since you are cutting out the overhead of a plugin framework, catch-all index pages, and theme abstraction), you shouldn't have too much of an issue. If you can afford dedicated server hosting, however, the trade-off between ease of use and the speed of development versus the cost of obtaining hosting should get you convinced with building your website with PHP.