When Should I Go For HTML5 & CSS3?

views:

473

answers:

+6 Q:

When Should I Go For HTML5 & CSS3?

Hello,

There is a lot of buzz about HTML5 and CSS3. How do I know that it's time to get started with them and use them straight away in my projects or how far are we from using them?

Update: I don't want to apply the rules of:

Graceful Degradation
Progressive Enhancement

I know if this is the case, then we can use them today.

+4 A:

Looking back at how long it took for most common browsers to support HTML4 and CSS1, I would predict that widespread HTML5 and CSS3 support will be available around year 2025.

jarnbjo 2010-02-14 13:11:18

You are not an optimist one, are you? : )

erenon 2010-02-14 13:13:20

Rather a realist. But who cares about HTML5? I mean, the most useful feature of HTML5 is without doubt the ability to embed media using the audio and video tags. Most browsers (expect IE) offer standard compliant implementations of these features already, but since the standard is not mandating support for specific media formats and the different browsers are not offering a common set of media decoders, the support is useless for the common web developer.

jarnbjo 2010-02-14 13:30:51

+11 A:

Go for HTML 5 now, but make sure your site degrades gracefully if the users browser don't support the latest technology. It's the primary solution for CSS3.

erenon 2010-02-14 13:11:53

Progressive enhancement, graceful degradation...

David Thomas 2010-02-14 13:13:40

+1 Graceful degradation is the key.

Vinko Vrsalovic 2010-02-14 13:14:22

If you still have to implement a "graceful degradation" solution for browsers without HTML5 support, why would you spend extra effort on HTML5, as the other solution will probably work on browsers with HTML5 support as well?

jarnbjo 2010-02-14 13:24:37

To provide the functionality you can't get without HTML5, of course. That's why it's called degradation, you lose some, but in a controlled manner.

Vinko Vrsalovic 2010-02-14 13:32:51

+21 A:

When can I use...

Marius 2010-02-14 13:13:57

@Marius: +1 Great share, thanks :)

Sarfraz 2010-02-14 13:19:20

conculsion: none is ready :( but you can still use drop shadows for example. It won't hurt if it doesn't appear

Omar Abid 2010-04-24 14:59:21

+2 A:

i think it also depends on what kind of application/website you are making and its target audience. if the target audience are expected to have a browser supporting the technologies you are intending to use, you are free to use them. otherwise, like ricebowl said "Progressive enhancement, graceful degradation" tho personally i don't really like having to clutter my code with "hacks" or fixes

iceangel89 2010-02-14 13:18:02

+3 A:

Another one, the famous list of Peter-Paul Koch:

http://www.quirksmode.org/compatibility.html

initall 2010-02-14 13:45:00

+3 A:

I am working in an environment where 90% uses IE7 and IE8, so I am reluctant to use HTML5 and CSS3 and then have to provide graceful degradation. It's like double the work, but same pay, and it violates the DRY (Don't Repeat Yourself) principle.

I guess it depends on whether you have fun tweaking css and javascript and have some spare time. If you do, then use HTML5 and CSS3 and provide graceful degradation. Otherwise..

I know this will slow down the adoption of HTML5 and CSS3, but when money and management talk, what can we do?

^_^

portoalet 2010-02-15 02:32:01

+1 A:

jmc734 2010-02-15 02:51:33

HTML5 and CSS3 are modular projects. They're supposed to be adopted part by part. You should talk about specific features or modules within the scope of these projects and ask if you can use them today.

There are things in HTML5 that are compatible with all older browsers, like the new doctype.

Then there are things that can be "faked" from javascript, like native json decoding, or local storage (with flash fallback).

It will take many years before you will be able to use the entire specs, but you don't have to wait for that.

Joeri Sebrechts 2010-02-15 10:24:30

start using it now and push your webvisitors to update their browser micro$oft is as usual the last one to inplement this stuff and hey now we can have fancy fonts loaded from our webserver.

Gos 2010-02-15 19:10:52

ansaurus

tags:

views:

answers:

When Should I Go For HTML5 & CSS3?

related questions