Category: Web Developing
Over the WebRTC, which doesn’t seem to be standardized.
Back in 2012, WebRTC, Google’s proposed web standard for audio, video chat and P2P file transfers, has gained a wide acceptance among various web browser vendors, including: Firefox, Opera, Maxthon and Google Chrome. While Apple is yet to implement and comment on WebRTC, Microsoft did raise some concerns and suggested their own web standard. That was back in August.
Free of charge.
If you had a PC in the 90s, there is a high probability that hearing someone say “Westwood Studios” will send shivers down your spine. Unfortunately, all good things come to an end. The studios were later bought out by the EA Games, a lot of people left to join Petroglyph Games, Command & Conquer franchise was turned into a joke and your childhood memories were pushed down the drain.
Christmas arrives early.
Now here is something to get done before the end of this year. According to the Worldwide Web Consortium (W3C), they have just finalized and published the specifications for Canvas 2D and HTML5. While that does not make them W3C standards just yet, there won’t be any more additions meaning that such specs are now feature complete so developers know exactly what to except and avoid the headaches in the future.
However, you will have to wait till the year 2014 because that’s when W3C plans to finalize the HTML5 standard.
Now here is something for the developers.
During Microsoft’s BUILD 2012 conference, Jatinder Mann the Program Manager for Internet Explorer, has shared an impressive amount of tips and tricks to speed up your applications and web sites.
The video below will tell you how to:
Ahead of its 2022 schedule.
Believe it or not but the original timeline to finalize HTML5 was ridiculous. Thankfully, the World Wide Web Consortium has changed its mind and is now targeting year 2014, which is far more reasonable.
As far as the schedule goes, W3C plans to release a HTML 5.0 Candidate Recommendation in late 2012 and HTML 5.1 in late 2016.
Thanks to various advancements in web standards and web browsers, developers are able to execute ideas that were never meant to be viewed as simple internet pages.
Google loosens its tie.
Back in June, the software giant has enabled the “Do Not Track” attribute by default on its IE10 web browser, then, following a huge uproar from the advertising agencies, W3C have decided to update their DNT specifications and asked web browser makers to have DNT disabled during initial software launch.
Wants more flexibility, a support for legacy devices.
Even though Google has proposed their own version of the WebRTC standard, it looks like the software giant has different ideas for the real time communication and they call it “Customizable, Ubiquitous Real Time Communication over the Web” or CU-RTC-Web.
So how exactly does it differ?