To quote the KWS wiki entry:
This specification defines a new API, focused on semantic language processing for two-way communication with a remote host. Eschewing typical binary protocols, this new interface creates a system-to-system forced sonic recognition on the receiving party.
The KWS definition page goes on to discuss key points like pending API access to the libation ES codebase, and encourages modification from the base parameters noting that each user has unique aptitudes in variety of related skills.
Indeed while some users, such as myself, have a low threshold for personal embarrassment (regardless of how many times a week I write these posts), I could possess high vocal aptitude that would mitigate a fond user experience if I were to stick with preset templates.
The spec deals with concerns such as bitrate, throttling, error mitigation, audio auth rights, P2P connectivity, and semantic packet delivery, but fails to touch on less favourable issues like hackers that implement auto-tuning modules.
Included with the announcement were two YouTube videos, one that explains the need for the new standard:
ARVE Error: no id set
And a second video that focuses on presenting the new KWS:
ARVE Error: no id set
Oddly the videos came along with a link “thebrowseryoulovedtohate.com” that’s got an extra ‘d’ in every instance?
The theme is apparently along the lines of “Have you tried IE Lately?”, with the assumption that you’ll like what you see.
I’m personally assuming that next week someone on the IE marketing team will get a phat bonus for a spike in downloads that doesn’t correlate to actual user shift.
In related news, FireFox has given up on 64bit development for now, listing a number of issues that make it a very wise decision, regardless of the folks that were ‘enjoying’ the struggle of maintaining a 64bit browser with very little 64bit extension support.
While a 64bit FireFox could theoretically run faster, the added expense of development was taxing the coders and holding back the progress of the browser vs. it’s competition.
If you MUST have a 64bit FireFox there is a build of FF with 64bit support, it’s called ‘WaterFox‘ and you can get it from Sourceforge.
Since I already had FireFox installed I grabbed the portable copy of WaterFox and it runs great, picking up most, if not all, of my FireFox profile/settings.
Personally? I’m using Chrome, and I am writing plugins for Chrome because I feel it’s going to win the browser war thanks to Android, Apple, and many other systems that use the WebKit engine by default.