Get used to HTML, then give CSS a shot. No reason to put it off longer than you have to, and it shouldn't be too hard to at least get started with. Once you have a prototype on the web, we can give you more feedback as well.
<offtopic>
Quote:
Originally Posted by Booooze
Don't count yourself out quite yet. There is still a need too make sites small and fast loading. I truly realized this since I moved out and have my internet setup as wireless (with cable a modem). Honestly, pages can take for ever. It's funny how we can send waves through the air faster (or as fast as) than the phone line. I am just really far from the router. It tends to be on and off.
|
The phone line (and most wired physical media) have the useful property of being quite reliable, whereas wireless is much less so (you might notice that you'll probably never actually get full throughput on a wireless network). Also, take into account the distance the signal has to transfer. 802.3u (100BaseTX) is supposed to handle distances up to 100m as I recall, which is still about double the range of 802.11n (according to a brief look at Wikipedia, as I'm not very familiar with wireless ranges). Actual throughput should be comparable for the two (100Mbps each direction for FE, and quoted avg. of 200Mbps for 802.11n, again from Wiki) though maxing that out seems like an abnormally high amount of traffic.
As to Internet speeds, the US has fairly low standards for broadband bandwidth. The best explanation I've come across as to why is that it would be nearly impossible for the ISPs to handle 300 million+ hosts and all their traffic at, say, 10Mbps (that's roughly 300M * 10Mbps, or 3Pbps if I did that right). Obviously, we don't all use our full bandwidth at once, but you can imagine how hard it would be to deal with even a fraction of that load.
</offtopic>