Coming to an e-book or car near you: the Web article tells that World Wide Web Consortium now have groups adapting Web technology for the automotive and publishing industries (traditionally two pretty narrow domains).
“The Web equals publishing,” Jaffe said. “There’s really no difference anymore.”
Interactivity is part of the reason the automotive industry is getting involved, too. Web technology can be used for writing in-car software.
The new directions follow in the footsteps of entertainment-industry players such as Netflix that climbed aboard the Web platform.
So don’t be surprised to see proprietary technology for e-book readers and in-dash computer systems slowly disappear in favor of software based on Web technology.
It isn’t always easy reconciling the philosophy of the Web with the demands of industry, though (for example idea of adding DRM to HTML5).
4 Comments
Tomi Engdahl says:
The Web Standards Project (WaSP) Shuttered
http://paritynews.com/web-news/item/737-the-web-standards-project-wasp-shuttered
Aaron Gustafson and two of his fellow contributors, Bruce Lawson and Steph Troeth, have announced the closure of The Web Standards Project (WaSP) which was formed back in 1998.
The primary goal of WaSP was to get browser makers support the open standards established by World Wide Web Consortium (W3C).
Gustafson notes in a post titled Our Work Here is Done, “Thanks to the hard work of countless WaSP members and supporters (like you), Tim Berners-Lee’s vision of the web as an open, accessible, and universal community is largely the reality.”
“While there is still work to be done, the sting of the WaSP is no longer necessary. And so it is time for us to close down The Web Standards Project”, he adds.
Tomi Engdahl says:
What Google’s WebKit Fork Means for the Web and Web Developers
http://www.webmonkey.com/2013/04/what-googles-webkit-fork-means-for-the-web-and-web-developers/
If you were secretly hoping that all web browsers would one day give up and adopt the WebKit rendering engine, we’ve got some bad news for you — Google just crushed those dreams.
Google has announced it is forking the WebKit rendering engine to create Blink, a new rendering engine for all Chromium-based web browsers — notably Chrome, Chromium, Opera and their mobile counterparts.
Blink will make its web debut in Chrome 28 (and Opera 14).
Based on Google’s Blink FAQ and initial announcement, expect Blink to diverge significantly from the WebKit project.
Tomi Engdahl says:
A Short Translation from Bullshit to English of Selected Portions of the Google Chrome Blink Developer FAQ
http://prng.net/blink-faq.html
1 Why is Chrome spawning a new browser engine?
The WebKit maintainers wouldn’t let us attack Apple directly, by changing WebKit in ways that would make it perform badly on OS X and iOS.
Because they share a rendering engine, developer effort to ensure Chrome compatibility currently benefits Apple platforms for free. To prevent this, we must make Chrome and WebKit behave differently.
1.1 What sorts of things should I expect from Chrome?
Nothing yet. This is a political move, not a technical one.
1.2 Is this new browser engine going to fragment the web platform’s compatibility more?
Yes.
1.6 So we have an even more fragmented mobile WebKit story?
Yes.
We encourage you to adopt Chrome on Android for your mobile browsing needs.
Tomi Engdahl says:
In for the long term: what HTML5 means to the auto industry
http://www.qnx.com/download/feature.html?programid=26052
HTML5 has become the most widely supported platform for mobile app development, giving auto companies access to a vast pool of developers and applications. It is also OS and hardware neutral, enabling companies to avoid vendor lock-in and to choose platforms that offer the greatest speed, reliability, or flexibility. Moreover, HTML5 can work in concert with other HMI technologies.