View Full Version : what do you think of

Jul 18th, 2002, 06:22 AM
ive only been using it for about 3 months.... how long does it take to get really good at it

Jul 18th, 2002, 08:15 AM
I've been writing stuff for about a couple of years now... it really depends on how often you build pages, and if you keep up with recent developments. I try and read a lot on various sites to keep up and forums like these are a great source for tips & tricks and solutions others found to their problems.
I guess you just keep learning and improving... :)

Jul 18th, 2002, 03:03 PM
yeah right; it's like how long is a piece of string - "good" is a very subjective word. I'd say prioritorise what you want to do - set benchmarks that are meaningful to you

Jul 18th, 2002, 09:44 PM
The long you use it the more you get to know it and be comfortable with it. But you never stop learning.;)

Jul 19th, 2002, 07:12 PM
I reckon that you cant get stuck in the boundarys of HTML, just expand beyond them... meaning if you think youve mastered HTML then there is always PHP/ASP/Whatever else to make what you know how to do better.... if you get my jist...

Keep at it :thumbsup:

Jul 19th, 2002, 08:27 PM
It's alot better now that I've semi-mastered CSS. :)

Jul 19th, 2002, 09:07 PM
Originally posted by mouse
It's alot better now that I've semi-mastered CSS. :)

Yeah CSS can do wonders and can save time.

Kang He
Jul 19th, 2002, 11:30 PM
I spent most of my time mastering tables and writing correct code in accordance to the W3C standards.. as tables are really mean and lean to structure your web site. Sometimes they do get complex, but if you use a little bit of commenting or identing here and there, everything should still go well :). Writing proper code instead of poorly coded and proprietary code isn't the easiest of all as well. Cross-browser support was hard, but fortunately as NS4.x use should insignificant (sorry justamom :p) by now, support for NS6.x, Mozilla, and IE4+ should not be too hard.

All in all, just keep it going :thumbsup:, try new things, and code often.

Jul 19th, 2002, 11:36 PM
Originally posted by Kang He
I spent most of my time mastering tables and writing correct code in accordance to the W3C standards.. as tables are really mean and lean to structure your web site.W3C have frowned upon the use of tables for page structure and use on non-data content for years.

Kang He
Jul 19th, 2002, 11:42 PM
Yes, they might prefer page layouts using CSS, but it gets messy with older browsers. And I prefer to have something more "concrete" to work with, if you understand what I mean.

I frown upon W3C's Microsoft technologies encouragement..

and I believe Jason also had something against their tutorials :confused:?

Jul 19th, 2002, 11:52 PM
Tables are good for content imo, sometimes they can mean you end up with 10 times the amount of code as with CSS, somethings are a real pain in the arse to do in CSS though; I use tables to keep my menu's together, in CSS it was never going to work...

Kang He
Jul 19th, 2002, 11:54 PM
Tables are also a lot easier regarding server-side applications generating content..

Jul 20th, 2002, 12:58 AM
Originally posted by Kang He
and I believe Jason also had something against their tutorials :confused:?

I have something against w3schools.com. But I promote W3C standards all over (and hence I promote Mozilla, because it is by far the best suite to use W3C standards with).

As for:

Originally posted by Kang He
Tables are also a lot easier regarding server-side applications generating content..

I'd have to differ. If you have a decent structure to your site, returing <div class="bla">some content</div> should make no difference in the same context as <tr><td>some content</td></tr>


What is really holding back CSS is IE. There are a lot of awesome, powerful features defined in the specs. Gecko has them, Opera has a lot of them, and IE doesn't. Until IE implements them, most developers won't begin to implement them. But until IE sees a market share taken away from them, they most probably won't implement anything (significant) new. Vicious cycle that can only be stopped by developers - you code for something, and people want to see the content, they may need to download a decent browser.

But that's a different argument all together, but before I started ranting, I was going to mention how IE makes table-less layouts a major pain to implement decently. I'll code up something in XHTML 1.1 that looks perfect in Gecko and Opera 6, only to find out (again, and again :() that IE's poor support of CSS2 is holding back this property from rendering, etc...

Jul 20th, 2002, 12:30 PM
i was kinda wondering why 'how long does it take to be good at html' ended up in a debate about how nice certain browsers or standards are or aren't ...
how long it takes to be 'good' depends on how 'good' u want to be... anyhow, i've been using html seriously for quite a few months now ... i started with just <marquee> and <img>, and not very long after that i could make 'something that resembled a decent webpage'. just get the hang of tables and divs and styles, (that doesn't take very long, if u're gonna take the time out for it), and u'll be able to make it work for you, the other tags mostly just fit in. of course tables are good for 'solid' stuff, but just for the layout i barely ever bother, i just use divs with stye="top:y;left:x"... pretty handy most of the time. but all the browser-compatibility stuff jkd said above was right, u might be as good as you want to be at html, but it's pain-staking to learn how to make ur html work everywhere. as far as i'm concerned i haven't done anything yet that i know will work on Gecko (that's right, jkd :p ) .... not that i haven't been thoroughly frustrated a couple of times at Microsoft's trying to be so different from everyone else, come to think of it ...

Jul 21st, 2002, 06:21 PM
Originally posted by ASAAKI
i started with just <marquee>...[/B]
*shudder* ;)

Jul 22nd, 2002, 10:49 PM
FWIW, I came to HTML from a programming background, so while I picked up the standards pretty quickly I had a number of rude awakenings on the cross-browser front. I suppose the best way to decide if you're any good is pretend you're working for a client and see if and when you can deliver whatever's required.

I suppose all the cross-browser stresses we have to put up with are character building. Certainly before I started coding web pages I never realised I could hate anything as much as Netscape.


Jul 23rd, 2002, 12:29 AM
let me tell you. Go to www.w3schools.com and you will master HTML in a week. It's all about memorizing codes. But most of it is common sense.