Opera Tech Break: HTML5


Uploaded by operasoftware on 03.11.2011

Transcript:
Oh! Hi, Zi Bin!
- Hey Bruce!
- How are you doing?
- Good, and you? - I’m very well, thank you.
- Nice hair style! - Nice hair style!
So this is Zi Bin Cheah, I’m Bruce Lawson. We work for Opera’s Developer Relations Team.
We talk about new technologies, and cool technologies.
One of the things we are always asked about is HTML5.
It’s the newest, coolest kid on the block; it’s the thing that everybody’s talking about.
It’s brand new, except it’s not brand new.
It started in 2004, in this very office you are looking at.
At 98 Waldemar Thranes gate in Oslo which is Opera Oslo headquarter.
So the first time you got Opera, Mozilla, Apple, Google, and Microsoft
- all working together, out in the open to make this specification together.
One of the primary aims of the spec is to ensure interoperability.
It’s mad and stupid if websites work in one or two of those browsers but not the other because consumers need the web everywhere.
One of the most interesting for developers about HTML5, or actually the least sexy side of it from a demo perspective,
is the fact that if a browser implements the HTML5 algorithms
doesn’t even matter if your web page has a broken mark-up, it will always be the same in every browser.
Let’s just call the “HTML5 parser.”
There is a Labs build on labs.opera.com
Its code name is Ragnarök - which means “end of the world” in Norwegian interestingly –
beginning of the brave new world - I’d like to think.
If you download that Labs build, we found in internal testing
20% of the all Opera’s site compatibility issues disappear like that.
For developers that’s great because things work everywhere. Of course for the consumer, that’s golden.
The web works wherever you can access the web, which is obviously a no-brainer.
These days a lot of marketing hype is focusing on HTML5, however if you really look at HTML5 it’s actually an evolution from HTML4.
So if you take a really old browser, for example IE6
and make it go through a HTML5 test, you actually realize that IE6 has very low score in HTML5.
That means that HTML5 has been happening since many years ago.
Just that it’s not called “HTML5”, but rather HTML5 in general.
Native apps will always be around. There are instances:
things like some games might run faster if they are written in C++ or Java natively on the platform.
- But those days are coming to an end I think. - These days people say you can write everything with Javascript.
So we’ve seen now a lot of games being written as HTML and Javascript apps that are actually web pages.
So your web app is simply a bookmark to a web page on the World Wide Web.
All these things that Bruce mentioned, it could only be done previously using Javascript or plug-in.
Now the emphasis is on the browser. Browser should and will be able to do all these things natively.
So this is Opera Mobile running on my Android phone. This is a Labs build - again labs.opera.com
– this is a web page, not an app. You need to sit there very still Zi Bin. I don’t know if it’s going to work with the lights and conditions here.
It’s a web page, and the web page is accessing a camera on my phone.
If Zi Bin stays very still
Hopefully that will do facial recognition and it’s drawing a magical HTML5 mustache where Zi Bin’s face was.
I think any technology if they can draw a magical mustache, it’s got to be the future.
Cheers developers!
Stay tuned to the next episode of Opera Tech Break.
Rock’n Roll in web standards!
Your boss might run in and say "I’ve got to have a HTML5 website!"
"My friend who’s a CEO of that company has a HTML5 website and I want one too!"
What you need to do is you go to the first line of your webpage and delete it.
You type in "‹!DOCTYPE html›", and you have a HTML5 website.
You get a massive pay rise, and you send 10% of it to Zi Bin and me for that handy tip.